-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Handle calico-rr nodes as workers so they get upgraded too #6447
Handle calico-rr nodes as workers so they get upgraded too #6447
Conversation
Hi @gaima8. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
I've modified another task to run on calico-rr nodes too in 8f2e263
Without this /usr/local/bin/calicoctl.sh doesn't get installed on the route reflectors during upgrade. This bit me during a 2.10.4 to 2.11.2 upgrade. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gaima8, Miouge1 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 |
/lgtm |
@gaima8 sorry for the long delay |
…s-sigs#6447) * Handle calico-rr nodes as workers so they get upgraded too * calico-rr nodes run 'calico and external cloud provider' too
What type of PR is this?
/kind bug
What this PR does / why we need it:
Route-reflector nodes don't get upgraded by upgrade-cluster.yml.
Which issue(s) this PR fixes:
Fixes #6386
Does this PR introduce a user-facing change?: