Emit an event when floating IP recreate fails midway
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
Research direction
Start in internal/provider/load_balancer.go at ensureLoadBalancer and trace the detach → delete → create path when allocator configuration changes. Inspect the branch where create fails after deletion, then run the relevant project checks and verify that the warning event and structured log identify the deleted old IP and failed recreation, with the event visible through kubectl describe svc.
Written by the indexing model from the issue text.
Description
Context
The recreate path in ensureLoadBalancer (internal/provider/load_balancer.go) runs detach → delete → create when the allocator config changes. If create fails after delete succeeds, the service is left with no floating IP until the next reconcile — and nothing tells the operator what happened or why.
Scope
Emit a warning event (and structured log) identifying the window: the old IP was deleted due to a config change and recreation failed. Should be visible via kubectl describe svc.
Done when
A create failure after delete is diagnosable from service events without reading CCM source code.
- 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
-
automation models
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug llm-stack needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Alert email subjects don't identify the host — same container on multiple hosts, identical subjectsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
P3 Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
grpc/grpc-go#9483 · 2 comments ·
Maintainers usually reply within 2 days
-
needs-area needs-kind needs-priority needs-status needs-triage
Difficulty 2/5 Under an hour Newbie friendliness 85/100
cncf/automation#736 ·
Maintainers usually reply within 1 day