Reject unsupported dual-stack service configurations
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go
- Domain
- cloud, networking
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.
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.
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2h 5m
- Merged PRs (30d)
- 14
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
-
enhancement low priority
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
eugenioenko/ttt#674 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
GoogleCloudPlatform/k8s-config-connector#13462 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
vavallee/bindery#2793 · 1 comment ·
Maintainers usually reply within 1 day