oxidecomputer / oxidecomputer/oxide-cloud-controller-manager
Reject unsupported dual-stack service configurations
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2h 5m
- Merged PRs (30d)
- 14
Description
Context
ipFamilies and ipFamilyPolicy are ignored by the load balancer implementation. A RequireDualStack service gets a single-family floating IP with no complaint — the CCM can only satisfy single-stack today (one floating IP per service).
Scope
Validate the service's IP family requirements in EnsureLoadBalancer (internal/provider/load_balancer.go) and reject configurations we can't satisfy (e.g., RequireDualStack), mirroring the existing externalTrafficPolicy check. Also consider consistency between ipFamilies and the oxide.computer/floating-ip-version annotation.
Done when
Dual-stack requests produce a clear error event instead of a silently wrong single-family IP.
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 in internal/provider/load_balancer.go at EnsureLoadBalancer and compare its validation with the existing externalTrafficPolicy check. Trace how ipFamilies, ipFamilyPolicy, and the oxide.computer/floating-ip-version annotation are represented, then verify that unsupported dual-stack requests produce a clear error event rather than a single-family floating IP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100