You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
eksctl and terraform bootstrap are amazing but there is also the possibility to bootstrap Crossplane with Crossplane.
Describe the solution you'd like
We can create bootstrap mechanism utilizing local(k3d/kind) Crossplane enabled bootstrap cluster to create EKS cluster including Crossplane installation and eventually hand over cluster control to itself.
This is interesting. One possibility that is useful is to spin up a Crossplane installation from a "root" AWS account into sub accounts for customers who may want to implement one Crossplane installation per AWS account.
I have being thinking on this use case, on creating AWS EKS Management configure with crossplane and deploy from kind, then delete kind the cluster.
What I'm thinking is how do you cleanly destroy this management cluster?
How well crossplane would manage itself? Like upgrades to of cluster control plane and nodes, great litmus test for HA
How to destroy itself cleanly?
Create a new kind cluster, use velero to capture the crossplane resources from eks cluster, deploy them into kind cluster, now kind cluster have full control over management cluster and delete the claim for the eks cluster.
Is your feature request related to a problem? Please describe
eksctl and terraform bootstrap are amazing but there is also the possibility to bootstrap Crossplane with Crossplane.
Describe the solution you'd like
We can create bootstrap mechanism utilizing local(k3d/kind) Crossplane enabled bootstrap cluster to create EKS cluster including Crossplane installation and eventually hand over cluster control to itself.
@vfarcic has a nice video illustrating this approach https://www.youtube.com/watch?v=IlaYGgyg06o ( the samples there are Azure ones but the approach is fully applicable to AWS)
The text was updated successfully, but these errors were encountered: