3.0.0

[Saranya-jena]

Introduction

This release is the result of a lot of extensive work and is packed with new features and improvements that are designed to make Chaos Engineering even better for our users. Here are some of the major feature additions:

Simplified User Experience

LitmusChaos 3.0.0 has undergone a complete transformation of our user interface (UX) to offer a sleek and intuitive experience. The new UI now leverages the Harness UIcore library, promising an even smoother user journey.

Introduction to Environments

Introducing Environments, a powerful tool that helps users effectively handle their Chaos Infrastructures and keep things organized.

Chaos Studio

Introduction of Chaos Studio, a one-stop solution to help users choose the faults based on use cases, tune them, add resilience probes and simplify the chaos experimentation.

Resilience Probes as an Entity

Now, resilience probes can be easily used over and over again, making it simple for users to create them once and benefit from them multiple times. This improvement ensures strong support for checking system stability and making it more resilient.

MongoDB High Availability Support

You can now install MongoDB Replicas via Helm using Bitnami Mongo, seamlessly integrating chaos engineering into your MongoDB infrastructure.

Terminology Changes

• Chaos Agents/Delegates are now referred to as Chaos Infrastructures.
• Chaos Scenarios/Workflows is now known as Chaos Experiments.
• Chaos Experiments have been rebranded as Chaos Faults.

Backward Compatibility

Litmus 3.x is not backward compatible with the older releases of ChaosCenter.

Release Cadence & Versioning

The release cadence & naming conventions continue to adhere to the principles followed thus far in the Litmus project: the monthly minor version releases (3.x.0) will happen on the 15th, with patch releases/hotfixes going into 3.x.x, on a need/demand basis. The 2.x version will be stopped at 2.14.x (2.14.0 at this point) and further patches will be made only upon request/community need.

Documentation

The documentation has undergone considerable changes - in terms of content and structure and it continues to undergo improvements as of the 3.0 release. We expect that a few more iterations are needed to sort out the Information Architecture.

The installation details for the 3.0 platform along with detailed introductions to concepts, architecture as well as a user guide are now available at https://docs.litmuschaos.io/

The latest chaos experiment details along with chaos custom resource schema specifications (tunables, examples, etc.,) and detailed FAQs & troubleshooting info can be found in https://litmuschaos.github.io/litmus/

For those continuing to use 2.x releases, please note that the docs are now moved to: https://v2-docs.litmuschaos.io/

Misc (monthly changelog between 15/09/2023 to 04/10/2023)

• fix: Updated config to fix favicon by @hrishavjha in fix: Updated config to fix favicon #4179
• fix: Added experiment run operator for NewChaosExperimentService by @amityt in fix: Added experiment run operator for NewChaosExperimentService #4184
• Fixed issue with invite user modal for users which were once deactivated by @Saranya-jena in Fixed issue with invite user modal for users which were once deactivated #4185
• fix: Fixed issues with refetch on ChaosHub, Environment and Probe screens by @hrishavjha in fix: Fixed issues with refetch on ChaosHub, Environment and Probe screens #4182
• fix: Fixed issue where create/edit environment API was being called twice by @hrishavjha in fix: Fixed issue where create/edit environment API was being called twice #4191
• Added check to prevent duplicate experiments with same name by @SarthakJain26 in Added check to prevent duplicate experiments with same name #4187
• [chore]: Show an error popup when a user enters an invalid info by @namkyu1999 in [chore]: Show an error popup when a user enters an invalid info #4177
• Adding event tracker changes for litmus 3.x by @imrajdas in Adding event tracker changes for litmus 3.x #4193
• fix: Fixing missing ResourceNames field from k8s probe by @S-ayanide in fix: Fixing missing ResourceNames field from k8s probe #4194
• Added loader component for Gitops page by @Saranya-jena in Added loader component for Gitops page #4192
• Removed system probe creation and updated lib images by @Saranya-jena in Removed system probe creation and updated lib images #4203
• added manifest changes for ci and 3.0.0 by @SarthakJain26 in added manifest changes for ci and 3.0.0 #4195
• Updated select probe button text by @Saranya-jena in Updated select probe button text #4204
• fix: update ChaosEngine crd manifest file in graphql server by @namkyu1999 in fix: update ChaosEngine crd manifest file in graphql server #4205
• added check to prevent dupicate experiment name by @SarthakJain26 in added check to prevent dupicate experiment name #4208
• chore(3.0.0): Adding the manifests for 3.0.0 by @ispeakc0de in chore(3.0.0): Adding the manifests for 3.0.0 #4196
• Fixed issue with fault node popover not showing probe results by @Saranya-jena in Fixed issue with fault node popover not showing probe results #4211
• fixed duplicate experiment name issue by @SarthakJain26 in fixed duplicate experiment name issue #4210
• Fix isRegistered check in GetK8sInfraYaml(ChaosCenter/graphql) by @Nageshbansal in Fix isRegistered check in GetK8sInfraYaml(ChaosCenter/graphql) #4127
• fix: Added minor changes for 3.0.0 artifacts by @Jonsy13 in fix: Added minor changes for 3.0.0 artifacts #4212

New Contributors

• @Nageshbansal made their first contribution in Fix isRegistered check in GetK8sInfraYaml(ChaosCenter/graphql) #4127

Full Changelog: 2.14.0...3.0.0

---

This discussion was created from the release 3.0.0.