oxidecomputer / oxidecomputer/cluster-api-provider-oxide
Consider ClusterResourceSet
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 1
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 6
Description
In order to stand up a function workload cluster, users should install at least a cni and the oxide ccm. Our WIP docs pr in oxidecomputer/cluster-api-provider-oxide#27 points users to our ccm helm chart and a calico yaml file on github, but users won't want to loop through this process for large numbers of clusters. CAPI provides a ClusterResourceSet resource that lives on the management cluster and populates resources on the workload cluster. We can optionally provide a CRS to template e.g. the oxide ccm on each workload cluster. Or we might determine that it's too much indirection, and recommend a better path to users. Either way, we should write down a determination and provide a better experience than "run this helm chart N times".
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 by reviewing the WIP docs PR in oxidecomputer/cluster-api-provider-oxide#27, the Oxide CCM Helm chart, the Calico YAML reference, and CAPI's ClusterResourceSet resource. Determine whether a CRS or another approach should manage these resources across workload clusters; done means the chosen path and rationale are documented with a repeatable user workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100