Skip to content

fix(envoy-gateway): use the real DigitalOcean LB-adoption annotation key - #25

Merged
jonathandieu merged 1 commit into
mainfrom
fix-envoy-gateway-lb-adoption-mechanism
Jul 10, 2026
Merged

fix(envoy-gateway): use the real DigitalOcean LB-adoption annotation key#25
jonathandieu merged 1 commit into
mainfrom
fix-envoy-gateway-lb-adoption-mechanism

Conversation

@jonathandieu

@jonathandieu jonathandieu commented Jul 10, 2026

Copy link
Copy Markdown
Owner

service.beta.kubernetes.io/do-loadbalancer-id is not a real DigitalOcean CCM
annotation - confirmed against DigitalOcean's official annotation reference
(https://github.com/digitalocean/digitalocean-cloud-controller-manager/blob/master/docs/controllers/services/annotations.md).
It never appears there. Every attempt to adopt the pre-existing, terraform-managed
Load Balancer failed silently and instead provisioned a new, untracked LB each time.

The correct annotation is kubernetes.digitalocean.com/load-balancer-id, confirmed
via DO's getting-started guide (https://github.com/digitalocean/digitalocean-cloud-controller-manager/blob/master/docs/getting-started.md).

Builds on #24 (EnvoyProxy/parametersRef mechanism), which was already correct -
only the annotation key value itself was wrong.

service.beta.kubernetes.io/do-loadbalancer-id is not a real DigitalOcean
CCM annotation - confirmed against DO's official annotation reference.
The correct key is kubernetes.digitalocean.com/load-balancer-id.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant