Closed asark67 closed 1 week ago
I had the same issue, I was able to fix it by enabling the eks-pod-identity-agent
in the eks cluster:
eks_addons = {
coredns = {
most_recent = true
}
vpc-cni = {
most_recent = true
}
kube-proxy = {
most_recent = true
}
eks-pod-identity-agent = {
most_recent = true
}
}
Although I see this thread configuration already has it, it may be worth checking if the pod identity association is using the correct role, you can list and check each:
aws eks list-pod-identity-associations --region <region> --cluster-name <cluster-name>
aws eks describe-pod-identity-association --cluster-name <cluster-name> --association-id <associationid>
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
This issue was automatically closed because of stale in 10 days
Description
When creating a cluster with karpenter the controller gives the above error. The VPC/Subnets are created separately and we are using private subnets only.
⚠️ Note
Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Versions
Module version [Required]:
Terraform version: Terraform v1.8.5
Provider version(s): on linux_amd64
provider registry.terraform.io/alekc/kubectl v2.0.4
provider registry.terraform.io/hashicorp/aws v5.50.0
provider registry.terraform.io/hashicorp/cloudinit v2.3.4
provider registry.terraform.io/hashicorp/helm v2.13.2
provider registry.terraform.io/hashicorp/null v3.2.2
provider registry.terraform.io/hashicorp/time v0.11.1
provider registry.terraform.io/hashicorp/tls v4.0.5
Reproduction Code [Required]
Service account exists:
Steps to reproduce the behaviour:
Points to note:
Expected behavior
EKS Cluster & Karpenter controller should come up cleanly
Actual behavior
EKS Cluster comes up cleanly Karpenter controller fails with error: {"level":"ERROR","time":"2024-06-30T11:45:00.909Z","logger":"controller","message":"ec2 api connectivity check failed","commit":"490ef94","error":"NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors"}
Terminal Output Screenshot(s)
Additional context
Running pods:-
ServiceAccount exists: