oxidecomputer / oxidecomputer/cluster-api-provider-oxide
Implement ClusterClass CRD
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 1
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 6
Description
ClusterClass is the new way to orchestrate cluster resources that moves the cluster-template.yaml client-side templating (via envsubst-ish) to server side. Patches to the ClusterClass resource during day-2 ops (like upgrades) are more gracefully orchestrated than template manipulation.
https://cluster-api.sigs.k8s.io/tasks/experimental-features/cluster-class/write-clusterclass
Contributor guide
No contributing guide indexed for this repository
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 with the linked ClusterClass documentation and compare its server-side model with the existing cluster-template.yaml client-side templating described in the issue. Trace where the provider handles cluster resources, then identify the entry points and tests involved in representing ClusterClass and day-2 patches. Done means ClusterClass resources are supported without relying on template manipulation and upgrades are orchestrated through their patches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend-api-design, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100