Hi! Anyone of you stumbled over those errors with an Rancher-created EKS Cluster? The AWS clusters are stable and I can create new clusters (even with same type and zone, named in the first message) and they won’t have this error message. Those errors are very sticky for months now and neither K8s (

1.19

-> `1.20`; triggered via Rancher) nor Rancher Update (

Rancher 2.5.9

-> `Rancher 2.6.7`; running on k3s) did solve this issue. Rancher is using

rancher/eks-operator:v1.1.5

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?