Emissary uses wrong TLSContext with identical name in different namespace

[dschuldt]

Describe the bug If two TLSContexts are present with an identical name but in different namespaces, Emissary does not use the one which resides in the same namespace as the Host resource.

To Reproduce

1. Create two namespaces
2. Create a TLSContexts and Hosts with the same names in these namespaces
3. Create two different certificates with different hostnames and configure the ambassador resources accordingly
4. You'll experience a host mismatch error and the wrong certificate is presented to user requests

Expected behavior Emissary should use the TLSContext within the same namespace as the Host

Versions (please complete the following information):

• docker.io/emissaryingress/emissary:3.6.0
• Rancher RKE Cluster v1.24.4

Additional context I'm sorry if I misunderstood the TLSContext resource. Is it not bound to a specific namespace?

Best Denis