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

Fix port number lookup of terminating pods #389

Merged
merged 1 commit into from
Sep 13, 2019
Merged

Conversation

jcmoraisjr
Copy link
Owner

Terminating pods are used on DrainSupport mode. They don't have endpoints so need their own func to find the correct container port if a named port is being used.

The service's target port should be a valid port number, which means it is the container port number, or should be a valid named port declared in the container. If the port is nether a valid number nor a declared named port, the endpoint of that pod will not be added.

Terminating pods are used on DrainSupport mode. They don't have endpoints so need their own func to find the correct container port if a named port is being used.

The service's target port should be a valid port number, which means it is the container port number, or should be a valid named port declared in the container. If the port is nether a valid number nor a declared named port, the endpoint of that pod will not be added.
@jcmoraisjr jcmoraisjr merged commit 2a195ad into master Sep 13, 2019
@jcmoraisjr jcmoraisjr deleted the jm-fix-drain-port branch September 13, 2019 11:14
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.

1 participant