again, the diagnostic service can help you here.

[ghostsquad]

I've seen this statement several times when I was attempting to get acquainted, and each time I saw this again, the diagnostic service can help you here., I was like, "Again?" When was I taught anything about this service?

Literally, you start here:
https://www.getambassador.io/docs/edge-stack/latest/tutorials/getting-started/

Then "What's Next?"

https://www.getambassador.io/docs/edge-stack/latest/topics/using/intro-mappings/

Doing a search for Diagnostics was less than useful too. 😞

https://www.getambassador.io/docs/edge-stack/latest/topics/running/diagnostics/#diagnostics
First sentence is:

If you're experiencing issues with Ambassador Edge Stack, log in to your Edge Policy Console...

Oh, well, I'm not using the service yet... so maybe this isn't the page.

Then I go here: https://www.getambassador.io/docs/edge-stack/latest/topics/running/debugging/ and see:

If you’re experiencing issues with the Ambassador Edge Stack and cannot diagnose the issue through the /ambassador/v0/diag/ diagnostics endpoint, this document covers various approaches and advanced use cases for debugging Ambassador Edge Stack issues.

This doesn't explain where this endpoint is located, or how to access it. Searching the page of /v0 has 1 entry, which is this sentence, which doesn't actually tell me anything.

Closest thing to useful was this:
https://www.getambassador.io/docs/edge-stack/latest/topics/running/ambassador/#observability

This page actually caused more confusion than anything:
https://www.getambassador.io/docs/edge-stack/latest/topics/install/docker/#2-productnames-diagnostics

I see several references to http://localhost:8080/qotm/ and http://localhost:8080/ambassador/v0/diag/

And if you look at the files that you asked to deploy (https://app.getambassador.io/yaml/edge-stack/2.1.2/aes.yaml) I see no reference to this path.

I never got this working properly at first because I just kept getting 301 redirects. After deploying the Host that allows insecure traffic, that's when I was able to visit that URL. See #503

Anyways... circles.. Sorry this was long, but I wanted to accurately try to reproduce what I ended up going through as I ran into several different, related, interconnected issues, documentation failures, and some other things (#502, emissary-ingress/emissary#4071, and emissary-ingress/emissary#4072)

Hindsight is 2020, if I port-forwarded directly to the admin port on the pod, I would have been able to see this, even while I was having the 301 redirect issue, and the TLS issues.