Configuring QoS for a Pod

Scenario

Specifications

The following table lists the bandwidth limitation specifications of pods.

• CCE DataPlane V2 is released with restrictions. To use this feature, submit a service ticket to CCE.
• After DataPlane V2 network acceleration is enabled, pods on HCE OS 2.0 use Earliest Departure Time (EDT) to limit the egress bandwidth. The ingress bandwidth limitation is not supported. In other network modes, a Token Bucket Filter (TBF) qdisc is used to limit the bandwidth.
• Pod bandwidth limitation applies to regular containers (runC as the container runtime), not secure containers (Kata Containers as the container runtime).
• Pod bandwidth limitation does not apply to hostNetwork pods.

Using the CCE Console

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