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

vSphere cluster upgrade failure : unrecognized feature gate: KubeletCredentialProviders #8984

Open
saiteja313 opened this issue Nov 7, 2024 · 0 comments

Comments

@saiteja313
Copy link
Contributor

What happened:

Upgrading EKS Anywhere cluster from 1.27 to 1.28. One version at a time.

  1. Took ETCD Cluster backup
  2. EKSA command line version 0.20.x
  3. executed eksa upgrade command. upgrade have scaled ETCD clusters from 3 to 6. Added two new controlplane (CP) nodes. Both CP nodes got stuck in NotReady status
  4. Checking the kubelet logs on the CP node, kubelet shows following error,
 kubelet[280524]: E1107 17:25:55.770885  280524 run.go:74] "command failed" err="failed to set feature gates from initial flags-based config: unrecognized feature gate: KubeletCredentialProviders"
  1. vi /etc/sysconfig/kubelet file, remove the --feature-gates=KubeletCredentialsProviders=true flag, save the file.
  2. kubelet gets auto restarted and joins the Kubernetes cluster
  3. Repeat the process for all CP and worker nodes to complete the upgrade.
  4. Checking the package controller, packager controller version is outdated with old version.

What you expected to happen:

  • EKSA should not add KubeletCredentialsProviders feature gate to kubelet configuration.

How to reproduce it (as minimally and precisely as possible):

  • upgrade cluster from 1.27 to 1.28 with old version of packages

Anything else we need to know?:

Environment:

  • EKS Anywhere Release: 0.20.8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant