Max Dribinsky

I think cloudstack work should be added to this issue

Is there any proposed solution for this issue? Are we considering delaying the EKS-A controller upgrade until after the components have moved to the bootstrap cluster? Or somehow separating the...

/cherrypick release-0.11

Some links: https://github.com/aws/eks-anywhere/blob/main/designs/full-cluster-lifecycle-api.md https://github.com/aws/eks-anywhere/compare/main...g-gaston:eks-anywhere:snow-controller-prototype?expand=1 And this is how snow generates capi objects: https://github.com/aws/eks-anywhere/blob/main/pkg/providers/snow/objects.go#L18. Reach out to @g-gaston for further questions

Discussing with @vivek-koppuru, he suggested performing a check prior to executing the move where we call `kubectl get clusters.cluster.x-k8s.io` and then looking at the `Status` field to make sure they...

/cherrypick release-0.11

discussing with @danbudris, it might make sense to introduce some validation on the webhook server service endpoints such as `https://eksa-webhook-service.eksa-system.svc:443/validate-anywhere-eks-amazonaws-com-v1alpha1-cloudstackdatacenterconfig?timeout=10s`

There appears to already be retry logic in place https://github.com/aws/eks-anywhere/blob/6104510c396ae57863b43a497f5c19c2293b8173/pkg/gitops/flux/client.go#L60-L65 so it's unclear why this operation might be failing. Next steps would include the following: 1. Fetch support bundle for...

/hold until CAPC v0.4.8 is released and built into EKS-A

>Interesting. How would the system reach this state? In order to use the new version of the code, the user has to run an upgrade command. And that upgrade command...