-
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
Guard External cloud controller manager with its feature flag #7770
Guard External cloud controller manager with its feature flag #7770
Conversation
Hi @mitch000001. Thanks for your PR. I'm waiting for a kubernetes 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. |
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.
/ok-to-test
/lgtm
744407c
to
5593efe
Compare
Previously when setting the external cloud controller manager configuration the core components `kubelet`, `apiserver` and `kubecontroller-manager` were configured to use the external cloud controller manager. Without setting the feature flag EnableExternalCloudController this lead to a cluster in which the masters had the cloud controller taint `node.cloudprovider.kubernetes.io/uninitialized` which prevents essential pods, like dns-controller to not be scheduled and leaves a cluster where worker nodes can't connect to the api server because they cannot resolve its hostname.
5593efe
to
92ffa79
Compare
@zetaab I fixed the bazel stuff. If it's green I am looking forward to your lgtm again :) |
/lgtm |
@rifelpet Can you review that, please? |
It looks good to me but I don’t have permission to approve the PR in order to get it merged, you’ll need one of the “approvers” in the OWNERS file to do that |
@mikesplain Can you give it a look and if you like what you see approve it? |
/test pull-kops-verify-staticcheck |
now that i'm an approver... /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mitch000001, rifelpet 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 |
Previously when setting the external cloud controller manager configuration the core components
kubelet
,apiserver
andkubecontroller-manager
were configured to use the external cloud controller manager. Without setting the feature flagEnableExternalCloudController
this lead to a cluster in which the masters had the node taintnode.cloudprovider.kubernetes.io/uninitialized
which prevents essential pods, like dns-controller to not be scheduled and leaves a cluster where worker nodes can't connect to the api server because they cannot resolve its hostname.