Network Overview

A single cluster provides different workload access types to address diverse scenarios. After a Service or ingress is created on the MCP console, the Service or ingress with the same name will be automatically created on each cluster deployed on this MCP instance. When a Service or ingress created on the MCP console is modified or deleted on the cluster console, a message is displayed indicating that the operation is successful. However, a Service or ingress with the same name will be automatically re-created.

• ClusterIP

  A workload can be accessed from other workloads in the same cluster through a cluster-internal domain name. A cluster-internal domain name is in the format of <User-defined Service name>.<Namespace of the workload>.svc.cluster.local, for example, nginx.default.svc.cluster.local.

• NodePort

  A workload can be accessed by other workloads in the same VPC using the IP address of a cluster node. The NodePort access type is applicable to the scenario in which other workloads in the same VPC in the cloud need to access the workload in the Kubernetes cluster.

• LoadBalancer

  A workload can be accessed from a public network through a load balancer. This access type is applicable to Services that need to be exposed to a public network in the system. The access address is in the format of <IP address of public network load balancer>:<access port>, for example, 10.117.117.117:80.

• Ingress

  Enhanced load balancer is used for an ingress. Compared with layer-4 load balancing, layer-7 load balancing newly supports Uniform Resource Identifiers (URI) configurations and distributes access traffic to the corresponding service based on the corresponding URIs. In addition, different functions are implemented based on various URIs. The access address is in the format of <IP address of public network load balancer>:<access port><defined URI>, for example, 10.117.117.117:80/helloworld.