Add multi-silo support
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
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.
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.
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2h 37m
- Merged PRs (30d)
- 11
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from oxidecomputer/oxide-cloud-controller-manager
-
Documentation Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
oxidecomputer/oxide-cloud-controller-manager#279 ·
Maintainers usually reply within 1 day
-
Documentation Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
oxidecomputer/oxide-cloud-controller-manager#278 ·
Maintainers usually reply within 1 day
-
Bug Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oxidecomputer/oxide-cloud-controller-manager#276 ·
Maintainers usually reply within 1 day
-
Bug Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oxidecomputer/oxide-cloud-controller-manager#275 · 1 comment ·
Maintainers usually reply within 1 day
-
Enhancement Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
oxidecomputer/oxide-cloud-controller-manager#274 ·
Maintainers usually reply within 1 day
All issues in oxidecomputer/oxide-cloud-controller-manager
Similar issues
-
Remove CAAPFOpenkind/chore kind/cleanup needs-area
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
rancher/turtles#2848 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
priority: low 🌱 type: enhancement 💅🏼
Difficulty 2/5 Half a day Newbie friendliness 84/100
nebari-dev/llm-serving-pack#199 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kedacore/keda#8225 · 1 comment ·
Maintainers usually reply within 1 day