Chaos Engineering was missing Harness CI/CD before buying ChaosNative

Harness’ purchase of ChaosNative not only shows how much chaos engineering integration was missing from its CI/CD platform, but also reflects Harness’ belief that capability is lacking in platforms. CDs/CDs in general.

In the immediate term, Harness will change the name from ChaosNative Litmus Enterprise to Harness Chaos Engineering and it will be available as a separate module. Harish will integrate ChaosNative Litmus Enterprise “very tightly” with the Harness CI/CD platform and it will be available among other “feature indicator” CI/CD tools, said Harish Doddala, senior director of product management for Harness. , The New Stack Harness seeks to integrate ChaosNative Litmus Enterprise into its platform in much the same way it sought to simplify its CI offering by turning Drone, which it purchased in 2020, into an open-source Harness CI Community Edition project.

However, that doesn’t mean DevOps teams won’t be able to use what will become the Harness Chaos Engineering module if they don’t adopt the Harness platform. It’s not ‘take it or leave it’ like using our platform or nothing,” Harness CMO Scott Sanchez told The New Stack. “If you have a different CI or CD platform and you want to embed this or another Harness module in it, it will definitely work.

Continuous expansion

Harness will continue to expand ChaosNative’s capabilities, including its plans to take a lead role in the open source development of LitmusChaos open source (Harness was not previously a major contributor to the project).

In other words, Harness has high hopes for the adoption of a standalone enterprise version of LitmusChaos, whether used with Harness or another CI/CD platform. Indeed, chaos engineering is sorely lacking in today’s CI/CD world, especially for highly complex and distributed microservices and Kubernetes environments, Doddala said.

“The creators of LitmusChaos have long noticed how many businesses need to do a lot of personalized experiences through chaos engineering,” Doddala said.

Emergence of chaos engineering

Chaos engineering has become an increasingly essential process for maintaining application reliability in cloud-native environments. Unlike pre-production testing, chaos engineering involves determining when and how software might break in production by testing it in a non-production scenario.

Think of chaos engineering as an overlap between reliability testing and experimentation of code and applications in a continuous integration/continuous delivery (CI/CD) pipeline, getting metrics and data on how an application can fail when certain errors are induced.

Specific to Harness-purchased ChaosNative offerings, ChaosNative Litmus Enterprise has helped DevOps and Site Reliability Engineers (SREs) adopt self-managed chaos engineering tools, while the cloud service, ChaosNative Litmus Cloud, offers a plan hosted LitmusChaos control.

Popular Alternatives

Indeed, chaos engineering has become increasingly critical for DevOps teams, especially those looking to gain agility by being able to apply chaos engineering early in the production cycle. It is also seen as a way to help break down the much talked about silos between developers, security team members and operations DevOps team members, allowing all teams to participate in chaos engineering without slowing down the production cycle.

ChaosNative Litmus Enterprise and ChaosNative Litmus Cloud are two popular alternatives on offer, Enterprise Management Associates (EMA) analyst Torsten Volk told The New Stack. “Shifting chaos to the left as an integral part of the CI/CD pipeline is crucial for successful digital transformation, as it instills a culture of accountability and reliability in product teams,” Volk said. “This lowers the threshold for leveraging already existing microservices to create innovative business solutions and thereby extracting more value from already existing code. So this makes the integration between chaos engineering and CI/CD pipeline automation very interesting for corporate clients.”

LitmusChaos was born out of a need to improve resiliency and “build trust in cloud-native services in production”. Uma Mukkara, The CEO of ChaosNative and maintainer of LitmusChaos, wrote in a blog post. “What started as an effort to provide out-of-the-box chaos experiences for Kubernetes-based microservices, eventually grew into an end-to-end framework for performing chaos engineering on a wide variety of application and infrastructure targets, with support for multi-tenancy, SLO validation, and custom workflows, among other features,” Mukkara wrote.

LitmusChaos was created in 2017 and was approved to become a Cloud Native Computing Foundation (CNCF) incubation project from a CNCF sandbox in January.

The open-source platform supports more than 50 chaos experiments “that span the gamut of Kubernetes resources,” Mukkara said earlier this year. These include major cloud platforms such as those offered by Amazon Web Services, Google Cloud Platform, and Azure, as well as applications such as Cassandra and Kafka.

Jack L. Goldstein