Clarify the use of the nodebalancer-id service annotation #392
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. 😄
Activity
rahulait commentedon May 24, 2025
Hi, please open a "support ticket" using https://cloud.linode.com/support so that they can provide correct steps.
asenci commentedon May 25, 2025
Hi @rahulait. Sorry, I meant clarify the usage in the documentation... 😅
I have found a couple more examples of people assuming an externally provisioned NodeBalancer could be used in the annotation, so I think it would save us a lot of trouble if the documentation was a bit more explicit about this requirement.
paulwalk commentedon Oct 26, 2026
Yes - I just hit exactly this confusion.