CCE provides the following access modes that allow access between applications in different scenarios:
An application can be accessed by other applications in the same cluster using an internal domain name. The internal domain name is in the format of <User-defined access mode>.<Namespace of the application>.svc.cluster.local, for example, nginx.default.svc.cluster.local.
An application can be accessed by other applications in the same VPC. The application can be accessed through the IP address of the cluster node or the service address of the ELB of the private network. The main scenarios are as follows: Other applications in the same VPC in the cloud need to access the application in the kubernetes cluster.
An EIP is used to access applications from a public network. This access mode is applicable to services that need to be exposed to a public network in the system. In this access mode, an EIP must be bound to a node in the cluster, and a port must be mapped to the node. The port range is 30000–32767. For example, the access address could be 10.0.0.0:30000.
This access mode is applicable to services that need to be exposed to public networks. Compared with EIP-based access, ELB allows access to applications from a public network with higher reliability. The access address consists of the IP address of an ELB service in the public network, followed by the configured access port number, for example, 10.117.117.117:80.
The difference between layer 7 load balancing and layer 4 load balancing is that layer 7 load balancing supports uniform resource identifier (URI) configuration and distributes access traffic to corresponding services based on the URI. In addition, the services implement different functions based on various URIs.
The layer 7 load balancing uses enhanced elastic load balancing. This access mode consists of the ELB service address of the public network, setting access port, and defined URI. For example, 10.154.55.77:80/helloworld.