-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Bump GCP CCM again #15972
Bump GCP CCM again #15972
Conversation
/test pull-kops-kubernetes-e2e-cos-gce-slow |
b75d68e
to
07c8520
Compare
/test pull-kops-kubernetes-e2e-cos-gce-slow |
/test pull-kops-kubernetes-e2e-cos-gce-serial |
So the permissions errors have been fixed but the CCM has this bug |
|
||
// Turn off some controllers if kops-controller is running them | ||
if clusterSpec.IsKopsControllerIPAM() { | ||
changes = append(changes, "-nodeipam", "-route") | ||
changes = append(changes, "-node-ipam-controller", "-node-route-controller") |
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.
controllers got renamed recently
mahamed REDACTED ~ $ docker run gcr.io/k8s-staging-cloud-provider-gcp/cloud-controller-manager:master --help | grep controllers
--controllers strings A list of controllers to enable. '*' enables all on-by-default controllers, 'foo' enables the controller named 'foo', '-foo' disables the controller named 'foo'.
All controllers: cloud-node-controller, cloud-node-lifecycle-controller, gkenetworkparamset, node-ipam-controller, node-route-controller, service-lb-controller
Disabled-by-default controllers: gkenetworkparamset (default [*
/test pull-kops-kubernetes-e2e-cos-gce-slow |
This can be merged now, test failures aren't related this change |
As long as |
It is optional /skip pull-kops-kubernetes-e2e-cos-gce-slow |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman 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 |
Repushed |
@upodroid: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
/lgtm |
/retest |
@justinsb mentioned some CCM bugs have been squashed since the 26.2.4 release.
We'll pin this to a release version soon