artifacthub helm/litmuschaos/litmus 2.13.0

latest releases: 3.12.0, 3.11.0, 3.10.0...
2 years ago

Release Notes (2.13.0)

Core Component Updates -

  • Enhance network experiments to derive IPs of the pods for Kubernetes service if the target pod has a service mesh sidecar. This will enable us to run all network chaos experiments with service mesh enabled effectively. litmuschaos/litmus-go#558

  • Adds Chaos SDK Templates for non-Kubernetes experiments (that is aws, gcp, vmware, azure) this will help us to speed up the experiment development process with a proper template for non-k8s services. To know more refer to the developer docs. litmuschaos/litmus-go#560

  • Fixes the stress-chaos experiments to run chaos (helper pod) with minimum capabilities. This will allow running the stress experiments in a restricted environment (like Openshift) with lesser capabilities as mentioned in SCC docs. litmuschaos/litmus-go#557

  • Enhance the HTTP status code experiment to have the ability to modify the response body. Also, it adds support to provide the content type and encoding for the body in modify body and status code experiment. litmuschaos/litmus-go#556

  • Adds the ability to provide custom Service Account value for helper pod using CHAOS_SERVICE_ACCOUNT Env. It is optional, if not provided the helper pod will run with the same service account as the experiment pod. litmuschaos/chaos-runner#178

  • Enhance chaos-operator to enable the leader-elect this ensures with multiple replicas a leader is elected and is the only one actively reconciling the set.litmuschaos/chaos-operator#417

  • Refactor chaos operator code to convert the History field in ChaosResult spec as a Go pointer. litmuschaos/chaos-operator#416

  • Enhance the chaos (helper pod) status check when waiting for completion with proper error handling. litmuschaos/litmus-go#552

  • Adds document content for a better understanding of new HTTP chaos experiments and tunables. #3755

ChaosCenter Updates -

  • Adds enhancement in chaos-scenarios replacing instance-id label with workflow-run-id, which is generated at runtime resulting in unique scenario/run creation on any scenario CRUD operations #3758

  • Upgraded chaos operator go-pkg to 2.12.0 in gql-server & subscriber introducing support for source imagePullSecrets in chaosEngine & along with updates in core components based on 2.12.0. #3759

  • Updated CRDs for ChaosEngines with source attributes updates in 2.12.0 CRD manifest #3742

  • Adds support for providing service-type & makes clusterIP as default service-type for all services in helm-chart litmuschaos/litmus-helm#257

LitmusCTL Updates -

Shoutouts!

Thanks to our existing and new contributors for this release- @chandra-dixit-hcl @alebcay @Jasstkn @amityt @Saranya-jena @SarthakJain26 @Adarshkumar14 @Jonsy13 @ispeakc0de @avaakash @uditgaurav

Installation

Litmus-2.13.0 (Stable) cluster scope manifest

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

Or

Litmus-2.13.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.13.0/litmus-portal-crds-2.13.0.yml
#Install ChaosCenter
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.13.0/litmus-namespaced-2.13.0.yaml -n litmus

Upgrading from 2.12.0 to 2.13.0

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

New Contributors

Full Changelog: 2.12.0...2.13.0

Don't miss a new litmus release

NewReleases is sending notifications on new releases.