Is it possible to reuse an existing AWS classic network load balancer when re-deploying Traefik (via the helm chart) ? When I run helm uninstall traefik it deletes the AWS classic network load balancer completely. Is there a way to specify the AWS classic network load balancer to use and stick with it always?
I found the following listed in the Kubernetes Service documentation :
service.kubernetes.io/tke-existed-lbid：<my-aws-classic-network-load-balancer-id-here>
Will adding the above annotation to the service just work and reuse my classic LB?
hello @nodesocket
Interesting use case, would you mind adding the mentioning annotation here
# - CurveP384
tlsOptions: {}
# Options for the main traefik service, where the entrypoints traffic comes
# from.
service:
enabled: true
type: LoadBalancer
# Additional annotations applied to both TCP and UDP services (e.g. for cloud provider specific config)
annotations: {}
# Additional annotations for TCP service only
annotationsTCP: {}
# Additional annotations for UDP service only
annotationsUDP: {}
# Additional service labels (e.g. for filtering Service by custom labels)
labels: {}
# Additional entries here will be added to the service spec.
# Cannot contain type, selector or ports entries.
spec: {}
# externalTrafficPolicy: Cluster
# loadBalancerIP: "1.2.3.4"
and verify if it works as we expected.
please keep us posted.
We are actually still on legacy version 1.7.30 so the annotation would be on:
traefik:
service:
annotations:
service.kubernetes.io/tke-existed-lbid：<my-aws-classic-network-load-balancer-id-here>
I believe. When I get some free time, I will try it in a dev cluster.