-
Notifications
You must be signed in to change notification settings - Fork 103
feat: drift for Kubelet Client ID #888
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
Merged
Merged
Conversation
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
32a9edf to
bbdeb68
Compare
matthchr
commented
May 14, 2025
charliedmcb
reviewed
May 15, 2025
charliedmcb
reviewed
May 15, 2025
Contributor
charliedmcb
left a comment
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.
Overall, looks good, but need to check the bootstrappingclient case
charliedmcb
reviewed
May 15, 2025
bbdeb68 to
6e4fe58
Compare
jackfrancis
reviewed
May 16, 2025
jackfrancis
reviewed
May 16, 2025
d7bf4c3 to
dfacd24
Compare
jackfrancis
reviewed
May 16, 2025
5cd7333 to
3eff98e
Compare
charliedmcb
reviewed
May 16, 2025
3eff98e to
0857587
Compare
charliedmcb
previously approved these changes
May 16, 2025
Contributor
charliedmcb
left a comment
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.
lgtm, assuming bootstrappingclient ordering is entirely covered.
pkg/providers/imagefamily/customscriptsbootstrap/provisionclientbootstrap.go
Show resolved
Hide resolved
* Add kubernetes.azure.com/kubelet-identity-client-id label to all nodes, to match what AKS does. * Drift nodes if the expected kubelet-identity-client-id has changed. * Does not drift if the node doesn't have the AKS Kubelet ClientID label set.
0857587 to
fd51e56
Compare
tallaxes
approved these changes
May 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
How was this change tested?
kubernetes.azure.com/kubelet-identity-client-id=fcd9a498-b00b-4757-8c2a-90f6ede47610. Changing it at the configmap scope results in drift and the new node coming up with the new label.Does this change impact docs?
Release Note