Help Center/ Cloud Container Engine/ User Guide (Paris Regions)/ Network/ Container Network Settings/ Configuring QoS Rate Limiting for Inter-Pod Access
Updated on 2024-01-26 GMT+08:00
View PDF
Share

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.

Constraints

The following shows constraints on setting the rate limiting for inter-pod access:

Constraint Type

Tunnel Network Model

VPC Network Model

Cloud Native 2.0 Network Model

Supported versions

All versions

Clusters of v1.19.10 and later

Clusters of v1.19.10 and later

Supported runtime types

Only common containers (runC as the container runtime) are supported.

Secure containers are not supported.

Only common containers (runC as the container runtime) are supported.

Secure containers (Kata as the container runtime) are not supported.

Only common containers (runC as the container runtime) are supported.

Secure containers (Kata as the container runtime) are not supported.

Supported pod types

Only non-HostNetwork pods

Supported scenarios

Inter-pod access, pods accessing nodes, and pods accessing services

Constraints

None

None
  • Pods access external cloud service CIDR blocks 100.64.0.0/10 and 214.0.0.0/8.
  • Traffic rate limiting of health check

Upper rate limit

Minimum value between the upper bandwidth limit and 34 Gbit/s

Minimum value between the upper bandwidth limit and 4.3 Gbit/s

Minimum value between the upper bandwidth limit and 4.3 Gbit/s

Lower rate limit

Only the rate limit of Kbit/s or higher is supported.

Currently, only the rate limit of Mbit/s or higher is supported.

Using the CCE Console

When creating a workload on the console, you can set pod ingress and egress bandwidth limits on the Advanced Settings > Network Configuration area.

Using kubectl

You can add annotations to a workload to specify its egress and ingress bandwidth. 
apiVersion: apps/v1
kind: Deployment
metadata:
  name: test
  namespace: default
  labels:
    app: test
spec:
  replicas: 2
  selector:
    matchLabels: 
      app: test
  template:
    metadata:
      labels:
        app: test
      annotations:
        kubernetes.io/ingress-bandwidth: 100M
        kubernetes.io/egress-bandwidth: 100M
    spec:
      containers:
        - name: container-1
          image: nginx:alpine
          imagePullPolicy: IfNotPresent
      imagePullSecrets:
        - name: default-secret
  • 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.

After modifying the ingress or egress bandwidth limit of a pod, restart the container for the modification to take effect. After annotations are modified in a pod not managed by workloads, the container will not be restarted, so the bandwidth limits do not take effect. You can create a pod again or manually restart the container.