Topic
In a rejected Kubecon San Diego proposal, I wanted to explore cluster migration at the trigger of a change in Crossplane resource classes.
Using an independent bucket, also provisioned by Crossplane, a single KubernetesCluster would be modified and the backing cluster would need to be archived, restored to a replacement cluster, and destroyed at the original location.
I believe there may be some rough edges in attempting to do this today, but those rough edges could inspire additional Crossplane features.
With some hand-holding, this concept could be possible using Velero (formerly Heptio Ark) as the archival mechanism.
I think this would make for a very interesting TBS episode.
Examples
https://velero.io/docs/v1.2.0/restore-reference/
Topic
In a rejected Kubecon San Diego proposal, I wanted to explore cluster migration at the trigger of a change in Crossplane resource classes.
Using an independent bucket, also provisioned by Crossplane, a single
KubernetesClusterwould be modified and the backing cluster would need to be archived, restored to a replacement cluster, and destroyed at the original location.I believe there may be some rough edges in attempting to do this today, but those rough edges could inspire additional Crossplane features.
With some hand-holding, this concept could be possible using Velero (formerly Heptio Ark) as the archival mechanism.
I think this would make for a very interesting TBS episode.
Examples
https://velero.io/docs/v1.2.0/restore-reference/