gentle-scooter-521310/21/2022, 7:05 AM
-> `1.20`; triggered via Rancher) nor Rancher Update (
-> `Rancher 2.6.7`; running on k3s) did solve this issue. Rancher is using
to handle the AWS communication atm. Any ideas besides recreating the AWS clusters and migrate the workload? Do you think it’s worth opening an issue in the eks-operator project?