oxidecomputer / oxidecomputer/oxide-cloud-controller-manager
Add multi-silo support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2h 5m
- Merged PRs (30d)
- 14
Description
The cloud controller manager currently supports a single Oxide silo, requiring all Kubernetes cluster nodes to reside in the same silo with a single API endpoint and credential set. This limits cluster topologies and prevents deployments that span multiple silos or racks.
This work adds support for multiple Oxide silos, allowing a single Kubernetes cluster to manage nodes across different silos — including silos on different racks. This aligns the CCM with how Oxide customers operating multi-rack environments will need to deploy Kubernetes.
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 reading the cloud controller manager's current single-silo configuration, API endpoint handling, and credential handling. Map how nodes are associated with a silo and define the multi-rack behavior; done means one Kubernetes cluster can manage nodes across multiple Oxide silos with the required endpoints and credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100