generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 324
Closed
Description
What happened:
Upgrading EKS Anywhere cluster from 1.27 to 1.28. One version at a time.
- Took ETCD Cluster backup
- EKSA command line version 0.20.x
- 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
- 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"
vi /etc/sysconfig/kubeletfile, remove the--feature-gates=KubeletCredentialsProviders=trueflag, save the file.- kubelet gets auto restarted and joins the Kubernetes cluster
- Repeat the process for all CP and worker nodes to complete the upgrade.
- 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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels