[self-hosted-pro] support configuring different internal and external URLs

[stefannica]

Contact Details [Optional]

No response

Feature Description

The internal communication between ZenML Pro components has to be done using a set of hostnames that is internal and separate from the hostnames used by the clients. This is particularly necessary when deploying ZenML on Kubernetes:

• the dashboard back-end connects to the control plane API using the internal control plane API URL
• the dashboard back-end connects to the ZenML Pro workspace API using the internal workspace API URL
• the workspace connects to the control plane API using the internal control plane API URL
• the dashboard front-end connects to the control plane API using the external control plane API URL (just as before)
• the dashboard front-end connects to the workspace API using the external workspace API URL (just as before)
• the dashboard front-end connects to the dashboard back-end using the external dashboard URL (just as before)
• the ZenML client connects to the workspace API using the external workspace API URL (just as before)
• the ZenML client connects to the control plane API using the external control plane API URL (just as before)
• any workloads that are running in the same cluster as the ZenML Pro workspace should use the internal workspace API

Supporting this will take some changes in the control plane and workspace configuration, as well as their Helm charts. It also requires a re-evaluation of the current cross-domain authentication scheme.

Problem or Use Case

No response

Proposed Solution

No response

Alternatives Considered

No response

Additional Context

No response

Priority

None

Code of Conduct

• I agree to follow this project's Code of Conduct