For some reason, after bumping to newer k8s libraries, one of the resources used for cilium switch were failing, blocking clusters from being deployed.
It's just quicker to remove all those resources and accept the fact we can't jump straight from v18 clusters to a release running this version of aws-operator.
For some reason, after bumping to newer k8s libraries, one of the resources used for cilium switch were failing, blocking clusters from being deployed. It's just quicker to remove all those resources and accept the fact we can't jump straight from v18 clusters to a release running this version of aws-operator.
Checklist