Closed aauren closed 1 month ago
This issue is currently awaiting triage.
If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
aws cloud provider uses the upstream kubernetes cloud library and the error is coming from the upstream code. It is using a different flag to override the kube config . Can you adding additional flag authentication-kubeconfig
and verify if it works. We can create an issue upstream and see how they would like to proceed.
Adding --authentication-kubeconfig
seemed to make the configuration work as well.
Can I ask why cloud-provider-aws has two separate flags for this? --kubeconfig
is the normal flag so I wasn't expecting to find another flag for passing the kubeconfig again.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
What happened:
I attempted to pass
--master
and--kubeconfig
tocloud-provider-aws
and didn't see any change to the output of the provider. This resulted incloud-provider-aws
not being configured correctly in my cluster.This resulted in the following error:
In the above,
10.96.0.1
is what the kube-apiserver would be reachable at, if my CNI was up and proxying requests to it's ClusterIP.What you expected to happen:
I expected it to adhere to the CLI arguments that I passed.
How to reproduce it (as minimally and precisely as possible):
--kubeconfig
or--master
and see thataws-cloud-controller-manager
does not follow the defined configurationAnything else we need to know?:
In my case, I found that this was caused by
aws-cloud-controller-manager
preferring the environment variables that Kubernetes sets:KUBERNETES_SERVICE_HOST
KUBERNETES_SERVICE_PORT
instead of the CLI parameters passed.
This will be surprising for most users as other CLI tooling from Kubernetes like
kubectl
prefer the CLI arguments over environment variables.It also makes it incredibly difficult to bootstrap a new cluster where the CNI is dependent on information from the cloud provider plugin in order to function correctly. As it will prefer the ClusterIP of the Kubernetes API server rather than the configuration that the user is attempting to override it with and result in a race condition.
Environment:
kubectl version
): v1.28.2aws-cloud-controller-manager
v1.29.1
Ubuntu 22.04.3 LTS
uname -a
):6.2.0-1018-aws
/kind bug