Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moving from 1.29 -> 1.30 using helm chart, cluster autoscaler fails with NoCredentialProviders: no valid providers in chain #6982

Open
zenbones opened this issue Jun 26, 2024 · 1 comment
Labels
area/cluster-autoscaler kind/bug Categorizes issue or PR as related to a bug.

Comments

@zenbones
Copy link

With the cluster-autoscaler, using the helm chart (both 9.36.0 and 9.37.0), in AAWS EKS, the component works fine in k8s 1.29 and fails in k8s 1.30 with...

I0626 21:53:36.018910 1 aws_manager.go:79] AWS SDK Version: 1.48.7
E0626 21:53:39.180984 1 aws_manager.go:128] Failed to regenerate ASG cache: NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
F0626 21:53:39.181014 1 aws_cloud_provider.go:455] Failed to create AWS Manager: NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors

The yaml for the autoscaler component and the aws-auth config maps are identical in both k8s versions, only the autoscaler runs fine in 1.29.

@zenbones zenbones added the kind/bug Categorizes issue or PR as related to a bug. label Jun 26, 2024
@adrianmoisey
Copy link
Contributor

/area cluster-autoscaler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cluster-autoscaler kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants