Closed surajrathoresp closed 1 year ago
@surajrathoresp, could you verify ccm is setup and running as expected on your cluster? For further details, please refer to the AWS cloud provider guide https://github.com/kubernetes/cloud-provider-aws/blob/master/docs/getting_started.md
@kishorj any document for k8 beginners on ccm?
as i am unable to do below steps mentioned in doc.
Temporarily stop the kube controller managers from running. This might be done by temporarily moving manifests out of kubelet's staticPodPath (or --pod-manifest-path), or scaling down the kube controller manager deployment, or using systemctl stop if they are managed by systemd. Add the --cloud-provider=external to the kube-controller-manager config. Add the --cloud-provider=external to the kube apiserver config. Add the --cloud-provider=external to each the kubelet's config. Add the tag kubernetes.io/cluster/your_cluster_id=owned (if resources are owned and managed by the cluster) or kubernetes.io/cluster/your_cluster_id=shared (if resources are shared between clusters, and should not be destroyed if the cluster is destroyed) to your instances. Apply the kustomize configuration: kubectl apply -k 'github.com/kubernetes/cloud-provider-aws/manifests/base/?ref=master' or run the cloud cloud controller manager in some alternative way.
The live docs for cloud-privider-aws is at the link https://cloud-provider-aws.sigs.k8s.io/. Which k8s distro do you use? For example: EKS, kops.
@surajrathoresp, I'm closing the issue. If you have further concerns, you can reopen or create a new issue.
I am facing the same problem with my self-managed, non-eks cluster...
I've solved this problem by manually adding EC2 instanceid
to the spec.providerID
field of each nodes
Hi team,
i deployed game-2048 yaml mentioned in your example config.
I have added below two lines in this yaml to work on AWS.
alb.ingress.kubernetes.io/subnets: subnet-14d98d63,subnet-0660433c632558877
alb.ingress.kubernetes.io/target-node-labels: worker=true
Environment
Problem Statement - all resources created as expected including ALB/TG/SG etc but there is no target attached in target group.
Getting below error in logs kubectl logs -n kube-system --tail -1 -l app.kubernetes.io/name=aws-load-balancer-controller|grep error
{"level":"error","ts":1671609090.8563244,"logger":"controller.targetGroupBinding","msg":"Reconciler error","reconciler group":"elbv2.k8s.aws","reconciler kind":"TargetGroupBinding","name":"k8s-game2048-service2-3546c1c632","namespace":"game-2048","error":"providerID is not specified for node: k8w1"}
exact error - providerID is not specified for node
I also tried with changing target-type but getting same error.
alb.ingress.kubernetes.io/target-type: instance
Additional Context:
How to fix this error to add targets in target group