Update hostname in docs?

[j08lue]

Docs such as these for the Device Auth Flow describe the target hostname as

https://auth-apx.${INGRESS_HOST}

The current develop cluster IAM service seems to be available at https://iam-auth.apx.develop.eoepca.org, though, i.e.

https://iam-auth.apx.${INGRESS_HOST}

While the original one throws a ERR_CERT_AUTHORITY_INVALID error (Subject: Kubernetes Ingress Controller Fake Certificate).

Should the URL be changed in the docs?

[w-jfe]

Hi Jonas, you refer to the deployment guide. This is not directly part of our IAM BB documentation.
Currently I can't find any more hostnames containing -iam or .apx there.
Apparently it has already been generalized. In my opinion, this generalization also makes sense for use by third parties. The hostnames do not necessarily have to be adopted as in the ArgoCD deployment.

To be on the safe side, I'll link Richard.

@rconway
Is the selection of hostnames generalized on purpose or should it rather be based on the current deployment in the deployment-guide?

[rconway]

@j08lue @w-jfe
The Deployment Guide (2.0-beta) has been refactored to focus on apisix - so the -apx qualifier is no longer required.
Additionally we used the generic host auth for the Keycloak ingress. This can be seen as an example name (and can be regarded as a configuration choice) - but is used consistently throughout the guide.
When we rebuild the dev cluster we should consider to realign with the Deployment Guide approach.