Help Center/ Cloud Container Engine/ User Guide (Paris Regions)/ FAQs/ Workload/ Container Configuration/ How Do I Set an FQDN for Accessing a Specified Container in the Same Namespace?
Updated on 2022-12-07 GMT+08:00

How Do I Set an FQDN for Accessing a Specified Container in the Same Namespace?

Context

When creating a workload, users can specify a container, pod, and namespace as an FQDN for accessing the container in the same namespace.

FQDN stands for Fully Qualified Domain Name, which contains both the host name and domain name. These two names are combined using a period (.).

For example, if the host name is bigserver and the domain name is mycompany.com, the FQDN is bigserver.mycompany.com.

Solution

Solution 1: Use the domain name for service discovery. The host name and namespace must be pre-configured. The domain name of the registered service is in the format of service name.namespace name.svc.cluster.local. The limitation of this solution is that the registration center must be deployed using containers.

Solution 2: Use the host network to deploy containers and then configure affinity between the containers and a node in the cluster. In this way, the service address (that is, the node address) of the containers can be determined. The registered address is the IP address of the node where the service is located. This solution allows you to deploy the registration center using VMs, whereas the disadvantage is that the host network is not as efficient as the container network.