Skip to content

2.11.0
Compare
Choose a tag to compare
@Jonsy13 Jonsy13 released this 15 Jul 06:10
2.11.0
84d7a63
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release Notes (2.11.0)

Core Component Updates -

  • Introduce different new HTTP chaos experiments for Kubernetes targets, this will allow users to introduce the following faults:

    • pod-http-status-code (modifies the status code of the response)
    • pod-http-modify-body (modifies the body of the response)
    • pod-http-modify-header (modify headers of incoming requests or the response from the service targetted)
    • pod-http-reset-peer (stops outgoing http requests by resetting the TCP connection)

    To know more checkout the experiment-docs.

  • Upgrade the operator SDK version to 1.14.0 for chaos operator and code refator for other litmus components to achieve compatibility.

  • Adds support for non-default vpc for the AWS ELB az-down experiment. As earlier the experiment only targets the ELB(s) that are associated with default vpc, so this will also allow the user to target the ELB(s) that are not associated with default vpc.

  • Enhance cmd probe spec to support different configuration for probe pod and containers like imagePullPolicy, cmd, args and so on. This will allow the user to run the cmd probe in more controlled way when used in source mode.

  • Fixes the error handling for application status check with litmus annotation for pod-level experiments.

  • Adds litmusctl docker image which will allow the users to install the agents (delegates) from a pod/container.

ChaosCenter Updates -

  • Updates terminologies for different entities -

    • Agents --> Chaos Delegates
    • Workflows --> Chaos Scenarios
    • Charts --> Chaos Experiments

  • Reduces the permissions in namespaced mode for execution plane components

  • Fixes an issue in SyncHub API when there is an error in communication between graphql-server and MongoDB and all hubs were getting deleted while trying to reclone current chaoshub.

NOTE: - Along with above terminologies updates, we will also be updating directory structure of ChaosHub for better readability and scalability of experiments and scenarios. With upcoming release, the charts will be renamed to experiments directory and workflows will be renamed to scenarios. Same changes have been already done in 2.11.0 version of ChaosHub. So, Users are requested to upgrade their ChaosHub directory structure with provided changes before upgrading to upcoming release - 2.12.0 version of ChaosCenter.

Installation

Litmus-2.11.0 (Stable) cluster scope manifest

kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.11.0/mkdocs/docs/2.11.0/litmus-2.11.0.yaml

Or

Litmus-2.11.0 (Stable) namespace scope manifest.

#Create a namespace eg: litmus
kubectl create ns litmus
#Install CRDs, if SELF_AGENT env is set to TRUE
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.11.0/litmus-portal-crds-2.11.0.yml
#Install ChaosCenter
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.11.0/litmus-namespaced-2.11.0.yaml -n litmus

Upgrading from 2.10.0 to 2.11.0

kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.11.0/mkdocs/docs/2.11.0/upgrade-agent.yaml
Assets 2
Loading
0 Join discussion