Kubernetes 1.11.x => 1.12.x AWS Cloud Provider fails to align AWSInstances <=> Kubernetes Instances about cloud-provider-aws

[danielsand]

side note:

node.Spec.ProviderID

is not set on the cluster nodes under 1.11.x

[varuns-zetaris]

Is there any solution to this issue. We are also facing the same problem when running k8s in AWS . I am trying under 1.12.x and still fails . Have added the required tags to worker and master in aws - kubernetes.io/cluster/ = owned . In logs of kubelet on worker it says the node registered successfully. However in controller manager the log says "node did not have ProvierID set"

[ArchiFleKs]

I had the same issue, are you using v1alpha3 ?

Here is my InitConfig :

---
apiVersion: kubeadm.k8s.io/v1alpha3
kind: InitConfiguration
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
  kubeletExtraArgs:
    cloud-provider: "aws"

It turns out that it is not use by the node, you need a JoinConfiguration:

apiVersion: kubeadm.k8s.io/v1alpha3
discoveryTokenAPIServers:
- 127.0.0.1:6443
discoveryTokenUnsafeSkipCAVerification: true
kind: JoinConfiguration
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
  kubeletExtraArgs:
    cloud-provider: "aws"

Mine was missing the AWS cloud provider therefore node were not using it and were not getting providerID.

[danielsand]

@ArchiFleKs thanks - that is a good hint.
I will try it out

[darwin67]

hit this issue as well and confirmed that adding cloud-provider: aws to node's kubelet args will resolve it

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.