Help Center> Cloud Container Engine> User Guide> Old Console> Workloads> Configuring QoS Rate Limiting for Inter-Pod Access
View PDF

Configuring QoS Rate Limiting for Inter-Pod Access

Scenario

Bandwidth preemption occurs between different containers deployed on the same node, which may cause service jitter. You can configure QoS rate limiting for inter-pod access to prevent this problem.

Notes and Constraints

  • Only clusters later than v1.19.10 are supported.
  • Only clusters that use the Cloud Native Network 2.0 and VPC network models are supported.
  • Only common containers (runC as the container runtime) are supported. Secure containers (Kata as the container runtime) are not supported.
  • CCE Turbo clusters do not support rate limiting when pods access cloud service CIDR blocks 100.64.0.0/10 and 214.0.0.0/8 or when pods access the ClusterIP Service in hostNetwork mode.
  • The QoS rate limiting lifecycle is the same as the pod lifecycle.

Procedure

You can add annotations to a pod to specify its egress and ingress bandwidth.

apiVersion: v1
kind: Pod
metadata:
  annotations:
    kubernetes.io/ingress-bandwidth: 100M
    kubernetes.io/egress-bandwidth: 100M
...
  • kubernetes.io/ingress-bandwidth: ingress bandwidth of the pod
  • kubernetes.io/egress-bandwidth: egress bandwidth of the pod

If these two parameters are not specified, the bandwidth is not limited.

Parent topic: Workloads