azure: Use internal K8s API endpoint for cloud-node-manager#17607
azure: Use internal K8s API endpoint for cloud-node-manager#17607k8s-ci-robot merged 1 commit intokubernetes:masterfrom
Conversation
Signed-off-by: Ciprian Hacman <ciprian@hakman.dev>
|
/lgtm |
|
/approve |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test pull-kops-e2e-azure-cni-cilium |
|
/override pull-kops-e2e-aws-upgrade-k133-ko133-to-klatest-kolatest-many-addons |
|
@hakman: Overrode contexts on behalf of hakman: pull-kops-e2e-aws-upgrade-k133-ko133-to-klatest-kolatest-many-addons DetailsIn response to this:
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-sigs/prow repository. |
cloud-node-manager needs to be able to remove the
node.cloudprovider.kubernetes.io/uninitializedtaint, before the CNI can run (e.g.cilium-operator)./cc @ameukam