oxidecomputer / oxidecomputer/oxide-cloud-controller-manager
Handle spec.loadBalancerIP
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2h 5m
- Merged PRs (30d)
- 14
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.
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
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.
Assessment
- Tech stack
- go
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100