Handle spec.loadBalancerIP
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, infrastructure
Research direction
Read internal/provider/load_balancer.go, focusing on addressAllocatorFromAnnotations and EnsureLoadBalancer. Trace how the annotation currently selects an explicit IP, then determine whether spec.loadBalancerIP should be supported or rejected, including disagreement handling. Done when setting the field no longer silently does nothing and the chosen behavior is clear.
Written by the indexing model from the issue text.
Description
Context
spec.loadBalancerIP is deprecated upstream but still widely used and widely expected to work. Today only the oxide.computer/floating-ip annotation selects an explicit IP; the field is silently ignored.
Scope
Either:
- Treat the field as equivalent to the
oxide.computer/floating-ipannotation (erroring if both are set and disagree), or - Reject services that set it, with a clear error pointing at the annotation.
Decision goes in addressAllocatorFromAnnotations / EnsureLoadBalancer (internal/provider/load_balancer.go).
Done when
Setting spec.loadBalancerIP either works or fails loudly — never silently does nothing.
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2h 37m
- Merged PRs (30d)
- 11
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
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
rossoctl/context-guru#346 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
prime-radiant-inc/evener#2883 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
gravitational/teleport#69805 ·
Maintainers usually reply within 11 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Under Poisson sampling, the `PLDAccountant` composes the inner event both before and after samplingOpen
Difficulty 2/5 Half a day Newbie friendliness 78/100
google/differential-privacy#496 ·