Pod network rate limit

Pod network rate limit is a Kubernetes pod-level chaos fault that generates Traffic Control (tc) rules with Token Bucket Filter (TBF) to assess Kubernetes pod resilience under limited network bandwidth condition.

Use cases

Pod network rate limit:

• Assess how well applications and services perform under constrained network bandwidth, helping identify potential bottlenecks and weaknesses.
• Ensure that critical services receive the necessary network bandwidth allocation while non-essential services are appropriately limited to maintain overall system stability.
• Evaluate the impact of network rate limits on security-related functions such as DDoS mitigation or intrusion detection, and assessing whether the system can withstand such scenarios.
• Determine the optimal network bandwidth allocation for different pods and applications to effectively plan resource usage and accommodate growth without degradation in performance.

Prerequisites

• Kubernetes > 1.16
• The application pods should be in the running state before and after injecting chaos.

Mandatory tunables

Tunable	Description	Notes
NETWORK_BANDWIDTH	Specify the network bandwidth rate limit	For more information, go to rate limit.
BURST	Specify the burst for the size of bucket, maximum amount of bytes that tokens can be available for instantaneously	For more information, go to rate limit.
LIMIT	Specify the limit for the number of bytes that can be queued waiting for tokens to become available	For more information, go to rate limit.

Optional tunables

Tunable	Description	Notes
MIN_BURST	Specify the size of the peakrate bucket	For more information, go to advance tunables.
PEAK_RATE	Specify the maximum depletion rate of the bucket	For more information, go to advance tunables.
NETWORK_INTERFACE	Name of the ethernet interface considered for shaping traffic.	For more information, go to network interface.
NODE_LABEL	Node label used to filter the target node if TARGET_NODE environment variable is not set.	It is mutually exclusive with the TARGET_NODE environment variable. If both are provided, the fault uses TARGET_NODE. For more information, go to node label.
TARGET_CONTAINER	Name of the container subject to network loss. Applicable for containerd and crio runtimes only.	With these runtimes, if the value is not provided, the fault injects chaos on the first container of the pod. For more information, go to target specific container.
CONTAINER_RUNTIME	Container runtime interface for the cluster.	Default: containerd. Supports docker, containerd and crio. For more information, go to container runtime.
SOCKET_PATH	Path of the containerd or crio or docker socket file.	Defaults to /run/containerd/containerd.sock. For more information, go to socket path.
TOTAL_CHAOS_DURATION	Duration to inject insert chaos (in seconds).	Default: 60 s. For more information, go to duration of the chaos.
TARGET_PODS	Comma-separated list of application pod names subject to pod network corruption.	If not provided, the fault selects target pods randomly based on provided appLabels. For more information, go to target specific pods.
DESTINATION_IPS	Comma-separated IP addresses and ports of the services or pods or the CIDR blocks (range of IPs) whose accessibility is impacted. Comma-separated IPs or CIDRs can be provided.	If the values are not provided, the fault induces network chaos for all IPs or destinations. For more information, go to destination IPs.
DESTINATION_HOSTS	DNS names or FQDN names of the services and ports whose accessibility is impacted.	If the values are not provided, the fault induces network chaos for all IPs or destinations or DESTINATION_IPS if already defined. For more information, go to destination hosts.
SOURCE_PORTS	Ports of the target application, the accessibility to which is impacted	Comma separated port(s) can be provided. If not provided, it will induce network chaos for all ports.
DESTINATION_PORTS	Ports of the destination services or pods or the CIDR blocks(range of IPs), the accessibility to which is impacted	Comma separated port(s) can be provided. If not provided, it will induce network chaos for all ports.
PODS_AFFECTED_PERC	Percentage of total pods to target. Provide numeric values.	Default: 0 (corresponds to 1 replica). For more information, go to pod affected percentage.
RAMP_TIME	Period to wait before and after injecting chaos (in seconds).	For example, 30 s. For more information, go to ramp time.
LIB_IMAGE	Image used to inject chaos.	Default: chaosnative/chaos-go-runner:main-latest. For more information, go to image used by the helper pod.
SEQUENCE	Sequence of chaos execution for multiple target pods.	Default: parallel. Supports serial and parallel. For more information, go to sequence of chaos execution.

Rate limit

• NETWORK_BANDWIDTH: It contains the network bandwidth rate limit
• BURST: It contains the size of bucket, maximum amount of bytes that tokens can be available for instantaneously
• LIMIT: It contains the limit for the number of bytes that can be queued waiting for tokens to become available

The following YAML snippet illustrates the use of this environment variable:

# it injects the network rate limit 
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: engine-nginx
spec:
  engineState: "active"
  annotationCheck: "false"
  appinfo:
    appns: "default"
    applabel: "app=nginx"
    appkind: "deployment"
  chaosServiceAccount: litmus-admin
  experiments:
  - name: pod-network-rate-limit
    spec:
      components:
        env:
        - name: NETWORK_BANDWIDTH
          value: "1mbit"
        - name: BURST
          value: "32kb"
        - name: LIMIT
          value: "2mb"
        - name: TOTAL_CHAOS_DURATION
          value: '60'

Advance tunables

• MIN_BURST: It contains the size of the peakrate bucket
• PEAK_RATE: It contains the maximum depletion rate of the bucket

The following YAML snippet illustrates the use of this environment variable:

# it injects the network rate limit 
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: engine-nginx
spec:
  engineState: "active"
  annotationCheck: "false"
  appinfo:
    appns: "default"
    applabel: "app=nginx"
    appkind: "deployment"
  chaosServiceAccount: litmus-admin
  experiments:
  - name: pod-network-rate-limit
    spec:
      components:
        env:
        - name: MIN_BURST
          value: '16kb'
        - name: PEAK_RATE
          value: '2mbit'
        - name: NETWORK_BANDWIDTH
          value: "1mbit"
        - name: BURST
          value: "32kb"
        - name: LIMIT
          value: "2mb"
        - name: TOTAL_CHAOS_DURATION
          value: '60'

Destination IPs and destination hosts

Default IPs and hosts whose traffic is interrupted because of the network faults. Tune it by using the DESTINATION_IPS and DESTINATION_HOSTS environment variables, respectively.

• DESTINATION_IPS: It contains the IP addresses and ports of the services or pods or the CIDR blocks (range of IPs) whose accessibility is impacted.
• DESTINATION_HOSTS: It contains the DNS names or FQDN names of the services and ports whose accessibility is impacted.

NOTE: Ports can be specified by using a pipe (|) as a separator. While providing ports is optional, omitting them will affect all ports associated with the destination IPs and hosts.

The following YAML snippet illustrates the use of these environment variables:

# it injects the chaos for the egress traffic for specific ips/hosts
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: engine-nginx
spec:
  engineState: "active"
  annotationCheck: "false"
  appinfo:
    appns: "default"
    applabel: "app=nginx"
    appkind: "deployment"
  chaosServiceAccount: litmus-admin
  experiments:
  - name: pod-network-rate-limit
    spec:
      components:
        env:
        - name: NETWORK_BANDWIDTH
          value: "1mbit"
        - name: BURST
          value: "32kb"
        - name: LIMIT
          value: "2mb"
        # supports comma separated destination ips
        - name: DESTINATION_IPS
          value: '8.8.8.8,192.168.5.6|80|8080'
        # supports comma separated destination hosts
        - name: DESTINATION_HOSTS
          value: 'nginx.default.svc.cluster.local|80,google.com'
        - name: TOTAL_CHAOS_DURATION
          value: '60'

Source and destination ports

By default, the network experiments disrupt traffic for all the source and destination ports. The interruption of specific port(s) can be tuned via SOURCE_PORTS and DESTINATION_PORTS ENV.

• SOURCE_PORTS: It contains ports of the target application, the accessibility to which is impacted
• DESTINATION_PORTS: It contains the ports of the destination services or pods or the CIDR blocks(range of IPs), the accessibility to which is impacted

Use the following example to tune this:

# it inject the chaos for the egress traffic for specific ports
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: engine-nginx
spec:
  engineState: "active"
  annotationCheck: "false"
  appinfo:
    appns: "default"
    applabel: "app=nginx"
    appkind: "deployment"
  chaosServiceAccount: litmus-admin
  experiments:
  - name: pod-network-rate-limit
    spec:
      components:
        env:
        - name: NETWORK_BANDWIDTH
          value: "1mbit"
        - name: BURST
          value: "32kb"
        - name: LIMIT
          value: "2mb"
        # supports comma separated source ports
        - name: SOURCE_PORTS
          value: '80'
        # supports comma separated destination ports
        - name: DESTINATION_PORTS
          value: '8080,9000'
        - name: TOTAL_CHAOS_DURATION
          value: '60'

Network interface

Name of the ethernet interface considered to shape the traffic. Its default value is eth0. Tune it by using the NETWORK_INTERFACE environment variable.

The following YAML snippet illustrates the use of this environment variable:

# provide the network interface
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: engine-nginx
spec:
  engineState: "active"
  annotationCheck: "false"
  appinfo:
    appns: "default"
    applabel: "app=nginx"
    appkind: "deployment"
  chaosServiceAccount: litmus-admin
  experiments:
  - name: pod-network-rate-limit
    spec:
      components:
        env:
        - name: NETWORK_BANDWIDTH
          value: "1mbit"
        - name: BURST
          value: "32kb"
        - name: LIMIT
          value: "2mb"
        # name of the network interface 
        - name: NETWORK_INTERFACE
          value: 'eth0'
        - name: TOTAL_CHAOS_DURATION
          value: '60'

Container runtime and socket path

The CONTAINER_RUNTIME and SOCKET_PATH environment variables to set the container runtime and socket file path, respectively.

• CONTAINER_RUNTIME: It supports docker, containerd, and crio runtimes. The default value is containerd.
• SOCKET_PATH: It contains path of containerd socket file by default(/run/containerd/containerd.sock). For docker, specify path as /var/run/docker.sock. For crio, specify path as /var/run/crio/crio.sock.

The following YAML snippet illustrates the use of these environment variables:

## provide the container runtime and socket file path
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: engine-nginx
spec:
  engineState: "active"
  annotationCheck: "false"
  appinfo:
    appns: "default"
    applabel: "app=nginx"
    appkind: "deployment"
  chaosServiceAccount: litmus-admin
  experiments:
  - name: pod-network-rate-limit
    spec:
      components:
        env:
        - name: NETWORK_BANDWIDTH
          value: "1mbit"
        - name: BURST
          value: "32kb"
        - name: LIMIT
          value: "2mb" 
        # runtime for the container
        # supports docker, containerd, crio
        - name: CONTAINER_RUNTIME
          value: 'containerd'
        # path of the socket file
        - name: SOCKET_PATH
          value: '/run/containerd/containerd.sock'
        - name: TOTAL_CHAOS_DURATION
          VALUE: '60'