Two tunnels behind LB - DNS records for apps

[rog_the_dodge]

Hi,

We have two tunnels (each with two replicas on K8s). We’ve defined a LB, with two pools - each pool having one origin (which represents the two replicas).

Before using a LB, we were defining our app dns records/routes on the one tunnel - and all worked fine. Now, we cannot do this for both tunnels, as - quite rightly - we’d have to define duplicate CNAMEs; one for each tunnel.

The LB itself is set to the zone apex name, which I take to mean being akin to a wildcard, but we’ll still need to create an ingress rule or otherwise on the tunnel config… or?

Ultimately, when using two tunnels behind a LB, where does one define the app DNS records? (Because it surely can’t be on each tunnel, due to duplicate records being a problem).

Many thanks!

[cscharff]

Set the load balancer name to the name of the application or change the cname you’ve been using to point to the apex name you’ve used to define your load balancer. Or create a different loadbalancer with the name of the app instead of the apex.

[rog_the_dodge]

Ah ha! I think you nailed it - it works just like any other LB elsewhere, then; nothing to do with tunnel routes as soon as you put an LB in front of it.

Will test it out and report back here for others who might also have shared my misunderstanding.

Thanks!