The primary use case for this is Kubernetes where the external and internal names will be different.
Within Kubernetes you address services by .. the service name will often include elements related to the deployment.
Eg Externally you might want to use ldap.example.org as the friendly name to display to the end user. Within the kubernetes cluster this may be openldap-master.internal.k8s.example.org where openldap-master is the service name, internal is the namespace and k8s.example.org is the cluster name
BertrandGouny
commented
5 years ago
The primary use case for this is Kubernetes where the external and internal names will be different. Within Kubernetes you address services by.. the service name will often include elements related to the deployment.
Eg Externally you might want to use
ldap.example.orgas the friendly name to display to the end user. Within the kubernetes cluster this may beopenldap-master.internal.k8s.example.orgwhereopenldap-masteris the service name,internalis the namespace andk8s.example.orgis the cluster name