To support workspaces, the data plane must be configured so that users can connect directly to the data plane to access interactive workloads, as described below.
The data plane must be served from a subdomain of the domain used for the control plane.
In other words, if users connect to Domino at example.com, then data planes must be served from data-plane.example.com.
The hostname above should resolve to a load balancer which routes traffic to port 8080 on Pods with the following label selector:
app.kubernetes.io/component: auth-proxy
app.kubernetes.io/instance: auth-proxy
app.kubernetes.io/name: auth-proxyYou can do this with a combination of a NodePort service and load balancer if on-premises, or using LoadBalancer service types in major cloud providers.
Users must connect to data planes using TLS (HTTPS). If you are using a load balancer to route traffic to the data plane, it might be easiest to configure the load balancer to serve valid TLS certificates for the domain.
-
Create a Kubernetes secret containing the certificates:
kubectl create secret tls custom-certs -n <data plane namespace> --cert=<cert file> --key=<key file> -
Set the following value when deploying the data plane Helm chart:
--set auth-proxy.config.nginx.tlsSecretName=custom-certs
If you are setting up Datasets for the first time, you’ll need to add a custom value to Helm first.