[RI-20] Populate Kubernetes topology labels from Oxide failure domains
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go, kubernetes
- Domain
- cloud, infrastructure
Research direction
Start with the CCM’s InstanceMetadata implementation and its Zone method, then trace how the Oxide API could expose a tenant-visible instance-to-failure-domain identifier. Coordinate that API dependency and verify that each failure domain produces a stable, distinct topology value so Kubernetes receives topology.kubernetes.io/zone labels rather than the generic sled value.
Written by the indexing model from the issue text.
Description
The CCM’s InstanceMetadata implementation returns provider ID, instance type, and node addresses but omits zone and region metadata. Kubernetes consequently receives no topology.kubernetes.io/zone label and cannot use scheduler topology constraints to spread workloads across Oxide failure domains.
Populate a stable, distinct topology value for each Oxide failure domain through InstanceMetadata.Zone. This may depend on the Oxide API exposing a tenant-visible instance-to-failure-domain identifier; coordinate that dependency rather than assigning every node the generic value sled.
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 3h
- Merged PRs (30d)
- 6
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: 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
-
Documentation Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Bug Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Bug Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oxidecomputer/oxide-cloud-controller-manager#275 · 1 comment ·
-
Enhancement Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
All issues in oxidecomputer/oxide-cloud-controller-manager
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
FootprintAI/Containarium#2338 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
SagerNet/sing-openvpn#11 ·
-
priority: P3 type: devops
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jiegui2025/hwspec#57 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
columnar-tech/dbc#513 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
streamplace/streamplace#1351 ·
Maintainers usually reply within 2 days