redpanda-data / redpanda-data/redpanda-operator
Figure out how to migrate CRDs across groups
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 84
- Forks
- 32
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 104
Description
Kubernetes has native support for versioning CRDs provided they remain within the same GroupVersion. We have ~2 concrete cases where we'll want to be able to migrate a CRD (and it's CRs) to a different GroupVersion, the Flux CRDs and operator V1's CRDs.
Ideally, we develop a generic/re-usable strategy that allows us to perform these types of migrations whenever.
VMWare has an unmaintained tool that does this: https://github.com/vmware-archive/crd-migration-tool.
We'll also want to make sure that this type of migration can be performed seamlessly when using terraform to manage a cluster.
JIRA Link: K8S-205
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced Flux CRD and operator V1 migration cases, the archived VMware crd-migration-tool, and the Terraform issue. Done means defining and implementing a generic, reusable strategy that migrates CRDs and their custom resources across groups and works seamlessly with Terraform-managed clusters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, terraform
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100