eks-anywhere: eksctl plan cluster upgrade command reports incorrect current versions
What happened:
when running eksctl anywhere upgrade plan cluster -f eksa-cluster.yaml the returned current versions are incorrect
What you expected to happen:
eksctl anywhere upgrade plan cluster -f eksa-cluster.yaml should report correct current and next versions
How to reproduce it (as minimally and precisely as possible):
run eksctl anywhere upgrade plan cluster -f eksa-cluster.yaml twice and you will see the 2nd run will report the same old versions under current
Anything else we need to know?:
$ eksctl anywhere upgrade plan cluster -f eksa-cluster.yaml
Warning: VSphereDatacenterConfig configured in insecure mode
Checking new release availability...
NAME CURRENT VERSION NEXT VERSION
EKS-A v0.10.1+c59d2cc v0.11.2+cd46e1d
Flux v0.29.4+e670ae4 v0.31.3+5738265
cert-manager v1.7.2+d4fa7e0 v1.8.2+543ab1d
cluster-api v1.1.3+d32ac08 v1.2.0+172e2ab
kubeadm v1.1.3+973f8a2 v1.2.0+525dbd6
vsphere v1.1.1+628bf01 v1.1.1+2fc04d0
kubeadm v1.1.3+9094d93 v1.2.0+115b0d5
etcdadm-bootstrap v1.0.3+bfb8d15 v1.0.5+77e4d45
etcdadm-controller v1.0.1+842bc86 v1.0.4+05b4294
cilium v1.10.11-eksa.2 v1.10.14-eksa.1
$ flux version
flux: v0.31.5
helm-controller: v0.22.2-eks-a-16
kustomize-controller: v0.26.3-eks-a-16
notification-controller: v0.24.1-eks-a-16
source-controller: v0.25.9-eks-a-16
Environment:
- EKS Anywhere Release: 0.11.2
- EKS Distro Release: 1.23
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 33 (19 by maintainers)
I would say to run
eksctl anywhere upgrade plan clusterand confirm that the versions are changing, and then to runeksctl anywhere upgrade clusterto see if the bundle ref changes and gets uploaded correctly to your repo. Run it with-v=6to see if we can see some more logs. Or-v=9if you don’t mind the verbosity.@echel0n Oh I see what you are saying, after running an upgrade it still shows the wrong current versions. Let me do some investigation on that.