Featured Webinar

Managing Chaos in a Cloud Native Development

Chaos Engineering is breaking barriers as the next-gen testing methodology and LitmusChaos is the go-to toolset preferred by Cloud Native developers & SREs. This talk touches upon the importance of Chaos testing and how it can be managed in a development environment using Litmus & Okteto.

ChaosNative Webinar

22 April, 2021 at 12:00 PM (EST)

*This webinar is over.
Watch the recorded session

About the speakers

Ramiro Berrelleza

Ramiro Berrelleza

Founder and CEO at Okteto

Entrepreneur and software engineer. Passionate about making software teams as productive as possible through the use of technology @okteto.com.

Uma Mukkara

Uma Mukkara

Co-Founder & CEO at ChaosNative

Passionate about solving user's problems. Love building great teams. Working on cloud native chaos engineering. Making resilience engineering easier for cloud native ecosystem.

Karthik Satchitanand

Karthik Satchitanand

Co-Founder & Lead, Open Source at ChaosNative

Spearheading open source at ChaosNative. Co-creator and maintainer of LitmusChaos. Open source innovation and working along with the community are the primary motivators.

About the webinar

The Cloud Native way of application development is experiencing a huge boost in the community giving rise to the need for resiliency & ease in deployment for these applications. With development, comes the responsibility of execution, management, & testing.
Okteto cloud gives instant access to secure Kubernetes namespaces to enable developers to code, build, and run Kubernetes applications entirely in the cloud.
Chaos Engineering is breaking barriers as the next-gen testing methodology and LitmusChaos is the go-to toolset preferred by Cloud Native developers & SREs. This talk touches upon the importance of Chaos testing and how it can be managed in a development environment using Litmus & Okteto.

Agenda

Intro to Chaos Engineering.

Why developers should care about Chaos Testing?

Chaos Testing patterns for Cloud Native Applications

Demo (LitmusChaos deployed Okteto, portal, run

experiments)

Transcript

“What does Chaos Engineering mean to cloud native developers?”

Uma Mukkara, CEO of ChaosNative began the webinar session by diving right into the topic this session addresses; Chaos Engineering for cloud native developers. He further talks about the increase of dynamism in applications due to the rise in adoption of microservices which in turn make the CI pipelines longer and more complex. Looking at these current changes to pipelines, the underlying infrastructure, and the microservices themselves, developers have been seeing a great need for Chaos Engineering. “Developers are now starting to see Chaos Testing as an extension of regular integration testing or unit testing.”


Accompanying Uma for this webinar were Ramiro Berrelleza, Co-founder & CEO of Okteto Cloud, and Karthik Satchitanand, ChaosNative Co-founder. They present details and give demonstrations of Litmus on Okteto and also about managing chaos, creating chaos workflows, and validating changes using Litmus & Okteto.


“Chaos engineering is rather a science of breaking things on purpose, and generally, so far it is being practiced by just SREs and QA Engineers, but we are seeing a lot of uptake of chaos engineering for developers,” Uma added.


Chaos Engineering is fueled by Kubernetes uptake itself. A lot of development has been witnessed in the cloud native domain nowadays and it is driven by Kubernetes crossing the chasm and entering the mainstream market.


Chaos Engineering has been in the limelight for about a year, people who have been using cloud native for a while now are already looking to implement chaos engineering to get the desired resilience. It is currently in the early market stage that allows us to build tools and platforms accordingly.




DEVELOPERS AND MICROSERVICES:


A developer’s working environment consists of unit tests before you actually merge the code, then come pipelines, where continuous integration tests are run and then these pipelines are extended for E2E tests.



So, what’s new for developers in cloud native?



  1. Microservices updates are coming faster than before.
  2. Pipelines are becoming longer and more complex.
  3. Developers need a way to suggest the underlying stack is behaving well by concentrating on codes and tests, and get the codes tested for faults in the dependencies simultaneously.



ASPECT OF CHAOS ENGINEERING FOR DEVELOPERS:


“We believe there is a great scope for Kubernetes developers because platforms like Okteto provide a suitable environment for them thereby generating a great need for chaos engineering,” Uma mentioned.


So, the basic code is run through the CI tests or pipelines, and in addition, we need to consider chaos testing or continuous verification keeping in mind the state of the platform and the microservices. Therefore, this cumulatively is called chaos engineering for developers.




CLOUD-NATIVE CHAOS ENGINEERING:


Principles of cloud-native chaos engineering:

  1. Open Source
  2. Community Collaborated
  3. Open API and lifecycle management
  4. Open Observability
  5. GitOps


Uma further added, “So these are the basic foundations on which we have built LitmusChaos and I am happy to inform you that we are capable of such logical functionalities of cloud native chaos engineering.”




LITMUSCHAOS PROJECT OVERVIEW:


LitmusChaos is an open-source toolset for practicing highly scalable chaos engineering practices in cloud-native environments.


Currently, it is a CNCF Sandbox project and has been applied for incubation in June 2021. It has ChaosNative, Amazon, and Intuit as the maintainers. LitmusChaos has 49 chaos experiments in total, 200,000+ experiment runs and 60,000+ installations. Community-wise, it consists of 600+ contributing members and 1600+ stars on GitHub.




LITMUS IN A NUTSHELL:


LitmusChaos

There is a cross-cloud control plane which is called Litmus Portal. We can cause chaos in the clusters where the portal is installed. We can register other portals as well into the clusters as targets. Chaos workflows are run on these clusters. There are certain agents which understand the user’s workflow and create the necessary chaos experiment pods and when we run them, we collect some information, there are chaos events that are generated, chaos metrics that are created, and all these are pulled by Prometheus. These can run on any Kubernetes cluster.




CHAOS ON CI PIPELINES:


In addition, LitmusChaos has been built to be suited for CI Pipelines. The entire Chaos Engineering infrastructure or architecture is built to be used through a library called Chaos CI library, which can be called from any existing CI pipelines, for example, GitLab, GitHub Actions, Keptn, Okteto, etc. by introducing additional chaos stage, and by calling this API, everything gets invoked automatically.



Uma hands over the mic to Ramiro who briefly takes us through what they do at Okteto, why it makes sense for Okteto and LitmusChaos to work together, and some of the use cases.



“Some observations from the field that I notice was-



  1. Applications are evolving towards microservices and other cloud-native patterns.
  2. Skew between development environments and production introduces extra work and expensive production issues.
  3. Developers spend a lot of time preparing for the work rather than actually doing it and delivering value.
  4. CI and shared integration environments become the bottleneck.” Ramiro says.


As developers in this domain, fast onboarding, realistic development or testing environments, instant feedback from coding locally, independence from the local machine, and no Kubernetes-based knowledge are some of the requirements that they need.


“Okteto is a developer platform powered by Kubernetes that lets your organization deploy fully configured, realistic development environments with one click,” Ramiro explains.



  • Okteto empowers developers by having the entire stack ready in one click, realistic development environments, and through continuous feedback while coding.
  • Okteto empowers teams by self-service access to the infrastructure, having Kubernetes namespaces on demand, and automatically freeing unused resources.
  • Okteto Cloud is ideal for the day-to-day development of cloud-native applications whereas Okteto Enterprise is for all the organizational features running on your Kubernetes infrastructure.



CHAOS TESTING OF OKTETO ON LITMUS


LitmusChaosLitmusChaos

Kartik and Ramiro go on to explain some basic functionalities of Litmus workings and its usage in Okteto with some insightful use cases towards the end of the session to give the viewers a clear understanding through the demo.

Sign Up

for our Newsletter

Get tips, best practices and updates on chaos engineeering in cloud native.

Videos

by Experts

Checkout our videos from the latest conferences and events

Our Videos

Want to make your
system more resilient?

Get LitmusGet Commercial Support