Spring Boot CPU Stress

Introduction¶

It can target random pods with a Spring Boot application and allows configuring the assaults to inject cpu-stress. Which attacks the CPU of the Java Virtual Machine. It tests the resiliency of the system when some applications are having unexpected faulty behavior.

Scenario: Stress CPU of Spring Boot Application

Uses¶

View the uses of the experiment

coming soon

Prerequisites¶

Verify the prerequisites

Ensure that Kubernetes Version > 1.16
Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here
Ensure that the spring-boot-cpu-stress experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here

Chaos Monkey Spring Boot dependency should be present in the application. It can be enabled in two ways:

Add internal dependency inside the spring boot application

Add Chaos Monkey for Spring Boot as dependency for your project

<dependency>
    <groupId>de.codecentric</groupId>
    <artifactId>chaos-monkey-spring-boot</artifactId>
    <version>2.6.1</version>
</dependency>

Start your Spring Boot App with the chaos-monkey spring profile enabled

java -jar your-app.jar --spring.profiles.active=chaos-monkey --chaos.monkey.enabled=true

Add as external dependency

You can extend your existing application with the chaos-monkey and add it as an external dependency at startup, for this it is necessary to use the PropertiesLauncher of Spring Boot

<dependency>
    <groupId>de.codecentric</groupId>
    <artifactId>chaos-monkey-spring-boot</artifactId>
    <classifier>jar-with-dependencies</classifier>
    <version>2.6.1</version>
</dependency>

Start your Spring Boot application, add Chaos Monkey for Spring Boot JAR and properties

java -cp your-app.jar -Dloader.path=chaos-monkey-spring-boot-2.6.1-jar-with-dependencies.jar org.springframework.boot.loader.PropertiesLauncher --spring.profiles.active=chaos-monkey --spring.config.location=file:./chaos-monkey.properties

Default Validations¶

View the default validations

Spring boot pods are healthy before and after chaos injection

Minimal RBAC configuration example (optional)¶

NOTE

If you are using this experiment as part of a litmus workflow scheduled constructed & executed from chaos-center, then you may be making use of the litmus-admin RBAC, which is pre-installed in the cluster as part of the agent setup.

View the Minimal RBAC permissions

apiVersion: v1
kind: ServiceAccount
metadata:
  name: spring-boot-cpu-stress-sa
  namespace: default
  labels:
    name: spring-boot-cpu-stress-sa
    app.kubernetes.io/part-of: litmus
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: spring-boot-cpu-stress-sa
  namespace: default
  labels:
    name: spring-boot-cpu-stress-sa
    app.kubernetes.io/part-of: litmus
rules:
  # Create and monitor the experiment & helper pods
  - apiGroups: [""]
    resources: ["pods"]
    verbs: ["create","delete","get","list","patch","update", "deletecollection"]
  # Performs CRUD operations on the events inside chaosengine and chaosresult
  - apiGroups: [""]
    resources: ["events"]
    verbs: ["create","get","list","patch","update"]
  # Track and get the runner, experiment, and helper pods log 
  - apiGroups: [""]
    resources: ["pods/log"]
    verbs: ["get","list","watch"]
  # for creating and managing to execute commands inside target container
  - apiGroups: [""]
    resources: ["pods/exec"]
    verbs: ["get","list","create"]
  # for configuring and monitor the experiment job by the chaos-runner pod
  - apiGroups: ["batch"]
    resources: ["jobs"]
    verbs: ["create","list","get","delete","deletecollection"]
  # for creation, status polling and deletion of litmus chaos resources used within a chaos workflow
  - apiGroups: ["litmuschaos.io"]
    resources: ["chaosengines","chaosexperiments","chaosresults"]
    verbs: ["create","list","get","patch","update","delete"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: spring-boot-cpu-stress-sa
  namespace: default
  labels:
    name: spring-boot-cpu-stress-sa
    app.kubernetes.io/part-of: litmus
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: spring-boot-cpu-stress-sa
subjects:
  - kind: ServiceAccount
    name: spring-boot-cpu-stress-sa
    namespace: default

Use this sample RBAC manifest to create a chaosServiceAccount in the desired (app) namespace. This example consists of the minimum necessary role permissions to execute the experiment.

Experiment tunables¶

check the experiment tunables

Mandatory Fields

Variables	Description	Notes
CM_PORT	It contains port of the spring boot application
CPU_LOAD_FRACTION	It contains fraction of CPU to be stressed, Eg: 0.95 equals 95%	Default value is 0.9. It supports a value in range [0.1,1.0]

Optional Fields

Variables	Description	Notes
CM_LEVEL	It contains number of requests are to be attacked, n value means nth request will be affected	Default value: 1, it lies in [1,10000] range
CM_WATCHED_CUSTOM_SERVICES	It limits watched packages/classes/methods, it contains comma seperated list of fully qualified packages(class and/or method names)	Default is an empty list, which means it will target all services
CM_WATCHERS	It contains comma separated list of watchers from the following watchers list [controller, restController, service, repository, component, webClient]	Default is `restController`
TOTAL_CHAOS_DURATION	The time duration for chaos injection (seconds)	Defaults to 30
SEQUENCE	It defines sequence of chaos execution for multiple target pods	Default value: parallel. Supported: serial, parallel
PODS_AFFECTED_PERC	The Percentage of total pods to target	Defaults to 0% (corresponds to 1 replica)
LIB	The chaos lib used to inject the chaos	Defaults to `litmus`. Supported `litmus` only
RAMP_TIME	Period to wait before and after injection of chaos in sec

Experiment Examples¶

Common Experiment Tunables¶

Refer the common attributes and Spring Boot specific tunable to tune the common tunables for all experiments and spring-boot specific tunables.

Spring Boot Application Port¶

It tunes the spring-boot application port via CM_PORT ENV

Use the following example to tune this:

# stress cpu of spring-boot application
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: spring-boot-chaos
  namespace: default
spec:
  appinfo:
    appns: 'default'
    applabel: 'app=spring-boot'
    appkind: 'deployment'
  # It can be active/stop
  engineState: 'active'
  chaosServiceAccount: spring-boot-cpu-stress-sa
  experiments:
    - name: spring-boot-cpu-stress
      spec:
        components:
          env:
            # port of the spring boot application
            - name: CM_PORT
              value: '8080'

CPU Load Fraction¶

It contains fraction of cpu to be stressed, 0.95 equals 95%. It can be tunes via CPU_LOAD_FRACTION ENV

Use the following example to tune this:

# provide the cpu load fraction to be stressed
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: spring-boot-chaos
  namespace: default
spec:
  appinfo:
    appns: 'default'
    applabel: 'app=spring-boot'
    appkind: 'deployment'
  # It can be active/stop
  engineState: 'active'
  chaosServiceAccount: spring-boot-cpu-stress-sa
  experiments:
    - name: spring-boot-cpu-stress
      spec:
        components:
          env:
            # it contains the fraction of the used CPU. Eg: 0.95 equals 95%.
            # it supports value in range [0.1,1.0]
            - name: CPU_LOAD_FRACTION
              value: '0.9'

            # port of the spring boot application
            - name: CM_PORT
              value: '8080'