Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle buggy case for headless Service with no port #366

Merged
merged 11 commits into from
Jan 25, 2019

Conversation

lblackstone
Copy link
Member

Fixes #248

Versions of k8s prior to 1.12.1 have a bug that affects
headless Services with no ports specified. These Services
do not get Endpoints assigned, which breaks the default
awaiter logic. This changeset skips the Pod ready checks
for Services affected by this bug.
Regex didn't work for multi-digit numbers.
pkg/await/core_service.go Outdated Show resolved Hide resolved
@lblackstone
Copy link
Member Author

Hmm, this fixes the bug, but broke unit tests due to a call to ServerVersion (not populated by the test mocks). Working on a fix now.

pkg/await/core_service.go Show resolved Hide resolved
pkg/await/core_service.go Outdated Show resolved Hide resolved
pkg/await/version.go Outdated Show resolved Hide resolved
pkg/await/core_service.go Outdated Show resolved Hide resolved
@lblackstone
Copy link
Member Author

Ok, pushed up a change that should fix unit tests, and I'll go back through and pull Patch out of the server version since I ended up not needing it anyway. (I mistakenly thought the bug was fixed in 1.12.1 rather than 1.12.0 initially).

serverVersion only includes Major.Minor and a separate
gitVersion type was created as a fallback option. Added
a test for parsing the gitVersion.
@lblackstone
Copy link
Member Author

@hausdorff Could you give this another look? CI failure is related to #375 - will rerun to get a ✅

@lblackstone lblackstone merged commit fb8073f into master Jan 25, 2019
@pulumi-bot pulumi-bot deleted the lblackstone/service-no-port-bug branch January 25, 2019 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants