Clarify lack of upgrade order for components#35572
Clarify lack of upgrade order for components#35572k8s-ci-robot merged 1 commit intokubernetes:mainfrom
Conversation
04271b6 to
cbb4644
Compare
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
Co-authored-by: Jordan Liggitt <jordan@liggitt.net>
cbb4644 to
93c2f67
Compare
|
/lgtm |
|
LGTM label has been added. DetailsGit tree hash: 756f3c9255b55eaa8c28eddee7e3cd8778265045 |
|
/lgtm Can you edit (in a followup?) perhaps line 116 to make it explicit that this means webhooks must be upgraded first? Webhooks need to be ahead of apiserver and tolerate requests from apiserver version N and N-1. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lavalamp, reylejano The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes #12323
Adds a sentence to say that there's no specific upgrade order required for
kube-controller-manager,kube-scheduler, andcloud-controller-manageras long askube-apiserveris upgraded first./sig docs
/language en
/cc @liggitt @lavalamp