Open dps-leemcneil opened 10 months ago
Attaching envoy.json
after running kubectl cp -n ambassador edge-stack-6567f8c455-bc8cs:/ambassador/envoy/envoy.json envoy.json
envoy.json
Hi @dps-leemcneil , I think we confirmed you created a wildcard host - can you share that wildcard Host here? I wonder if it has an ambassador_id or some config issue such that it isn't getting recognized. I notice the virtual wildcard host in the envoy config is giving a 404. Also, do you see your Hosts return a 'ready' state if you run
kubectl get Hosts
or even just checking one of them, ie kubectl get web-frontend.example.com
?
I'm having a problem with URL paths such as
/.ambassador/oauth2/multicookie
(or anything /.ambassador) will return a 404 when I use a Host resource.When the Host is removed, the .ambassador paths work again.
I am trying to setup the OAuth2 filter (Azure AAD), and have multiple Host resources (hostnames) pointing at different services. However whenever I add a Host, the .ambassador paths are no longer possible to reach.
Is it possible to add a Mapping to get the .ambassador URLs working within a Host?
To Reproduce Create
Service
andMapping
:This works and
/.ambassador/oauth2/...
endpoints are available.If I now add a
Host
with or without a TLS cert, all/.ambassador/oauth2/...
endpoints 404.Expected behavior Expecting that
/.ambassador/oauth2/...
endpoints are available on a definedHost
resource. Currently only on the default host, noHost
resources (for example different hostnames with TLS certs).Versions (please complete the following information):
Additional context Add any other context about the problem here.