-
Notifications
You must be signed in to change notification settings - Fork 41.5k
Build node health-check URL using NodeAddresses #7114
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A loop with a score function is scary to me. What do you think about building a map and expressing priority based on execution order? Something similar to GetHostIP() in the kubelet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this code should be functionally identical to that code, but without the temporary map.
GetHostIP is much clearer, so I can do that. It sounds like maybe we are going to remove this check entirely though, depending on when #7092 lands. (Some initial discussion in #7115)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah #7092 has some interesting implications. Does #7182 unbreak AWS for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would generally assume that #7092 is aspirational until someone is signed up to work on it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#7182 does/should unbreak AWS for now - it would be good to get that merged!
AWS needs this and #7115 if I wanted to change the node name to the EC2 instance id, which would be great to do long-term. In #7182 I put out the fire, so this can wait until #7092 is implemented.
I don't suppose there's a different reason to merge this and/or #7115? @cjcullen you mentioned you were also looking at this (for a different reason, I guess)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar reason... It would be nice to remove the requirement that the master must have DNS cname record entries for nodes that match their k8s names (or the value passed in with --hostname_override). We have that Addresses field on the nodes which I think was added for exactly this type of thing.
I'm interested to see where #7092 goes, but as long as we have Master->Kubelet communication, I think it would be useful to get this change in. It'll make this use case cleaner, and hopefully guide new code away from using Node.Name as a resolvable address.