Help Center/ Cloud Container Instance (CCI)/ User Guide/ Using CCI Through the Console/ Network Management/ Services/ Service Overview
Updated on 2026-04-28 GMT+08:00
View PDF
Share

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 supports Services of the LoadBalancer type.

Workloads can be accessed over a private or public network:

  • Private network access: Create a Service of the LoadBalancer type, with a private network load balancer associated and use the private IP address of this load balancer to access the workload. You can also configure a trustlist or blocklist for access control. This method can be used in the following scenarios: mutual access between workloads in the same namespace, mutual access between workloads and other cloud resources (such as ECSs) in the same VPC, and mutual access between workloads in different namespaces of the same VPC. Workloads are accessed 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, with a public network load balancer associated, and use the public IP address and port of this load balancer to access the workload over 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 only have IPv4 IP addresses. IPv6 addresses are not supported.
  • 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. If the add-on version is earlier than 1.5.5, Services of the LoadBalancer type are not supported.
  • After a Service of the LoadBalancer type is created, the listener's protocol cannot be changed (for example, the protocol cannot be changed from TCP to UDP or from HTTP to HTTPS). To change the protocol, you need to delete the Service and create another one.
Parent Topic: Services