linode / linode/linode-cloud-controller-manager
Clarify the use of the nodebalancer-id service annotation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 94
- Forks
- 75
- Avg merge
- 11h 19m
- Merged PRs (30d)
- 20
Description
The documentation says the `nodebalancer-id` service annotation can be used to re-use an existing NodeBalancer instead of creating a new one, but it does not make it clear the exiting NodeBalancer needs to be provisioned by Kubernetes/CCM in the first place.
Trying to use an externally provisioned NodeBalancer results in the service being stuck in `Pending` state and CCM returning a 403 error: `Error syncing load balancer: failed to ensure load balancer: [403] Unauthorized`
It would be preferable that we could use a manually provisioned NodeBalancer so we can control the lifecycle independently from the Kubernetes service, but since it is not possible at the moment, it should be made clear this is not supported. 😄
Contributor guide
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 with the documentation for the `nodebalancer-id` service annotation and review its current description against the reported 403 error and Pending state. Clarify that the existing NodeBalancer must have been provisioned by Kubernetes/CCM, and state that externally provisioned NodeBalancers are not supported; done means the limitation is unambiguous to users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100