Updated on 2025-08-12 GMT+08:00

Service Overview

A Service is a resource used to define a pod network access interface. It allows a group of pods to be accessed in a stable manner so you do not need to consider the location and quantity of the pods. CCI 2.0 supports Services of the LoadBalancer type.

Workloads can be accessed over a private or public network, and they can also access the public network.

  • Private network access: Create a Service of the LoadBalancer type, configure a private network load balancer, and use the private IP address of the private network load balancer to access the workload. You can also configure a trustlist and blocklist for access control. This method can be used in the following scenarios: mutual access between workloads in the same namespace, mutual access between other cloud resources (such as ECSs) and CCI 2.0 workloads in the same VPC, and mutual access between workloads in different namespaces of the same VPC. Services are provided over the private network through the private IP address and port of the load balancer in the format of <private-IP-address>:<port>.
  • Public network access: Create a Service of the LoadBalancer type and configure a public network load balancer. You can use the public IP address and port of the load balancer to access the workload from the public network. You can also configure a trustlist or blocklist for access control.

Constraints on Services

  • For Services of the LoadBalancer type, only dedicated load balancers are available. If a Service of the LoadBalancer type is used, the pods can have IPv4 IP addresses.
  • If the CCE Cloud Bursting Engine for CCI add-on is used to schedule the workloads to CCI 2.0, dedicated load balancers can be configured for ingresses and Services of the LoadBalancer type. The CCE Cloud Bursting Engine for CCI add-on does not support Services of the LoadBalancer type if its version is earlier than 1.5.5.