kubermatic / kubermatic/machine-controller
Future API group conflict with upstream CAPI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 326
- Forks
- 138
- Avg merge
- 2d 46m
- Merged PRs (30d)
- 12
Description
Hi,
we are currently using the machine-controller as an addon of Kubeone, in its default configuration.
I was wondering why the CRDs of CAPI (machinedeployments, machinesets, machines) are of the cluster.k8s.io api group and not of the upstream CAPI cluster.x-k8s.io api group? I noticed, that CAPI switched from *k8s.io to *x-k8s.io a while ago.
Are there plans using the same api group as upstream CAPI in future?
For us this is important, because we are thinking of deploying a CAPI in the Kubeone cluster running the machine-controller, therefore we would like to ensure, that no conflicts regarding the CRDs occur.
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 comparing the machine-controller CRDs for machinedeployments, machinesets, and machines with upstream CAPI's cluster.x-k8s.io API group. Determine whether an API-group migration or compatibility decision is required; done means the future API-group plan and conflict behavior are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100