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
kubeadm: print all the kubelets and nodes that need to be upgraded on "upgrade plan" #123578
Conversation
Skipping CI for Draft Pull Request. |
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.
/retitle kubeadm: print all the kubelets and nodes that need to be upgraded on "upgrade plan"
/approve
/hold
/release-note-edit
|
/triage accepted |
/cc @pacoxu |
8b317b1
to
cb1c284
Compare
f1c1297
to
aa851fd
Compare
} | ||
|
||
// Get the lastest cluster version | ||
clusterVersion, err := getLatestClusterVersion(kubeAPIServerVersions) |
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.
just to check the logic.
we take the latest apiserver version as the cluster version, but we make sure to show a warning to the user if there are diff apiserver versions?
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.
L88-L95 has printed the message. Do you mean that moving the logic into the getLatestClusterVersion func?
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.
tested locally, but only with one node. this works great from what i can tell.
thanks @carlory
/lgtm
/approve
/hold cancel
/retest
LGTM label has been added. Git tree hash: e5bae1c6208626df2fca6e9fe5449323e345443b
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: carlory, neolit123 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
See #123461 (comment)
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: