artifacthub helm/litmuschaos/litmus 2.4.0

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

Core Component Updates

  • Fixes the permission issue faced by container user (of different litmus components) to access its directory in an Openshift cluster as the openshift cluster runs the container with an arbitrary uid in the root group.

  • Enhance the stress chaos experiments to gracefully terminate the stress process in case it is not completed and remove on its own.

  • Enhance the node drain experiment to skip the uncordon step post chaos if the target node is not available. It occurs if we enable the autoscaling for the node pool on the cloud provider.

  • Updates the experiment contributing docs with the usage of litmus SDK and also adds the chaos-chart details in the repo readme.

  • Adds an overview section in litmus-python with the detailed steps for preparing and using the experiment and workflows in python.

  • Adds new e2e-pipeline for testing the vm-ware experiments from hub. It supports both nightly and manual builds.

  • Enhance the e2e-dashboard to show the logs of the tests running in the e2e pipeline.

  • Enhance GitHub Chaos Actions to support AWS EKS clusters, with this now we can integrate any external EKS cluster with chaos action to run the experiments.

Chaos Center Updates

  • Upgrading argo workflow and event tracker API versions to support chaos center on Kubernetes 1.22.0+

  • Addition of a new event tracker policy operator (known as Change) to track values of any field in the Kubernetes resource and removed the dependency of event tracker from last applied configuration annnotation

  • Addition of new permissions to docker images of ChaosCenter server to OpenShift friendly

  • Migration of APIs from graphql-server to auth-server and introduction of gRPC for the internal communication

  • Addition of "--skipSSL" flag in litmusctl to disable SSL for the communication between control-plane and execution plan

  • IPV6 support for control plane

  • Addition of new E2E tests for observability.

Notes

  • The CRDs for ChaosCenter will be versioned now . So, CRDs for ChaosCenter v2.x.x will be available in 2.x.x branch.
  • The Project DB migration has been done in this release along with some enhancements (like addition of new flag --skipSSL), so any version of litmusctl below v0.7.0 won't be compatible with ChaosCenter 2.4.0 or above.

Installation

Litmus-2.4.0 (Stable) Cluster Scope manifest

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

Or

Litmus-2.4.0 (Stable) namespace scope manifest.

export LITMUS_PORTAL_NAMESPACE="<namespace>"
kubectl create ns ${LITMUS_PORTAL_NAMESPACE}
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.4.0/litmus-portal/litmus-portal-crds.yml
curl https://raw.githubusercontent.com/litmuschaos/litmus/2.4.0/mkdocs/docs/2.4.0/litmus-namespaced-2.4.0.yaml --output litmus-portal-namespaced-k8s-template.yml
envsubst '${LITMUS_PORTAL_NAMESPACE}' < litmus-portal-namespaced-k8s-template.yml > ${LITMUS_PORTAL_NAMESPACE}-ns-scoped-litmus-portal-manifest.yml
kubectl apply -f ${LITMUS_PORTAL_NAMESPACE}-ns-scoped-litmus-portal-manifest.yml -n ${LITMUS_PORTAL_NAMESPACE}

Shoutouts!

Thanks to our existing and new contributors for this release- @Aman-Codes @DhananjayPurohit @tuananh @andrewhu-hcl @Vr00mm @nicjohnson145 @DarthBenro008 @mehabhalodiya @bbarin @amityt @gdsoumya @Saranya-jena @SarthakJain26 @ispeakc0de @Jonsy13 @rajdas98 @uditgaurav

Don't miss a new litmus release

NewReleases is sending notifications on new releases.