LitmusChaos at Kubecon EU '21
Tags: kubernetes, cloudnative, litmuschaos, opensource
Published: 2021-05-19 15:48:27

KubeCon is veritably a festival for the tech community nowadays, and this is a sentiment that I have expressed several times before, but cannot tire of repeating! The sheer diversity of content (organized into a neat set of tracks), the announcements & launches, predictions, and panel discussions, all add to the excitement. I even managed to get my young nephew interested in the Cloud Native world by ordering the Phippy & friends buildable set with my Speaker giveaway! 

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/owfs7o8h7yuzgrv9ikdb.png)

For us, as members of the LitmusChaos project & the broader cloud native chaos engineering community, this edition of Kubecon EU '21  turned out to be sweeter still.  

The predictions made ahead of the event by Cheryl Hung, VP, Ecosystem at CNCF, where she noted the growing interest in chaos, set the ball rolling (and this came on the back of similar observations made by Liz Rice, the chair of CNCF’s Technical Oversight Committee (ToC) at the November 2020 Kubecon): 

![image](https://user-images.githubusercontent.com/21166217/118844085-4be2a480-b8e8-11eb-9f05-fbee16fd4b7f.png)

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">From inside CNCF I have a unique insight into cloud native tech, DevOps and ecosystem. Here’s what I see coming next!<a href="https://t.co/KeqcQCC3E7">https://t.co/KeqcQCC3E7</a> <a href="https://t.co/e7uoq0aXXz">pic.twitter.com/e7uoq0aXXz</a></p>&mdash; Cheryl Hung (@oicheryl) <a href="https://twitter.com/oicheryl/status/1374419739489886212?ref_src=twsrc%5Etfw">March 23, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

This added to the organic interest that Litmus as a project has gathered in the CNCF community, and resulted in some wonderful responses to the various presentations/talks that it featured in. All this led to newer slack members, appreciative messages from those that grokked the project, more questions on what’s coming & roadmap, quick feedback from folks that tried it, and some cool issues and PRs in the process! 

In this blog post, let us do a quick round-up of the talks/sessions where Litmus “appeared”. Some of the perspectives expressed are instructive and definitely hold value for us at the project. I have also tried to capture all the buzz (via tweets, of course) around Litmus and provide links to the awesome presentations around the project.

# The Round-Up

First up, was the whirlwind sandbox projects tour by Justin Cormack, CTO, Docker,  where he [introduced Litmus](https://youtu.be/XmMbzBuCuYw?t=462) as a way to package & perform your own custom chaos experiments. The talk prompted some awesome cloud-native advocates & tech-gurus to recall some deep dives on the project that had been performed in recent times! 


![image](https://user-images.githubusercontent.com/21166217/118844394-8d734f80-b8e8-11eb-9796-aaa59049aa73.png)

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">This year we&#39;ve been taking a deep dive into the CNCF Sandbox on our blog, and so far we&#39;ve covered <a href="https://twitter.com/kubevirt?ref_src=twsrc%5Etfw">@kubevirt</a>, <a href="https://twitter.com/LitmusChaos?ref_src=twsrc%5Etfw">@LitmusChaos</a> and <a href="https://twitter.com/telepresenceio?ref_src=twsrc%5Etfw">@telepresenceio</a>. But <a href="https://twitter.com/justincormack?ref_src=twsrc%5Etfw">@justincormack</a> just blew us out of the water running through all 50 projects in 15min! <a href="https://twitter.com/hashtag/KubeCon?src=hash&amp;ref_src=twsrc%5Etfw">#KubeCon</a><a href="https://t.co/qh9eVE4q3N">https://t.co/qh9eVE4q3N</a></p>&mdash; LiveWyer (@LiveWyerUK) <a href="https://twitter.com/LiveWyerUK/status/1389891093605634051?ref_src=twsrc%5Etfw">May 5, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

![image](https://user-images.githubusercontent.com/21166217/118844649-bdbaee00-b8e8-11eb-903f-360dc41516ca.png)
 
<blockquote class="twitter-tweet"><p lang="und" dir="ltr"><a href="https://twitter.com/LitmusChaos?ref_src=twsrc%5Etfw">@LitmusChaos</a> <a href="https://t.co/U405GfALZZ">https://t.co/U405GfALZZ</a></p>&mdash; David McKay (@rawkode) <a href="https://twitter.com/rawkode/status/1389873545497522176?ref_src=twsrc%5Etfw">May 5, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

Our KubeCon talk, on [Putting Chaos into Continuous Delivery to increase Application resilience](https://www.youtube.com/watch?v=_DgCc4-BLW8) along with the fantastic team at Keptn, was well attended with many questions on the philosophy of automated chaos. For those interested, there is more coming on the integration with Keptn, including some very cool use cases around auto-remediation!  

![image](https://user-images.githubusercontent.com/21166217/118845328-50f42380-b8e9-11eb-9037-915e7d99afaf.png)

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Key takeaways from the talk! 😍<br>Glad to have <a href="https://twitter.com/KitopiHQ?ref_src=twsrc%5Etfw">@KitopiHQ</a> as an adopter of both <a href="https://twitter.com/keptnProject?ref_src=twsrc%5Etfw">@keptnProject</a> &amp; <a href="https://twitter.com/LitmusChaos?ref_src=twsrc%5Etfw">@LitmusChaos</a>.<br><br>This establishes a process of continuously evaluating resiliency! <a href="https://t.co/Rs8QvoKogk">pic.twitter.com/Rs8QvoKogk</a></p>&mdash; LitmusChaos (Chaos Engineering for Kubernetes) (@LitmusChaos) <a href="https://twitter.com/LitmusChaos/status/1390245923633078275?ref_src=twsrc%5Etfw">May 6, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> 

Alois Reitbauer (https://twitter.com/AloisReitbauer), co-chair of the CNCF SIG-App Delivery, presented [some interesting findings in this space](https://youtu.be/74VpVe-pZx0?t=1481), with Chaos Engineering & Litmus getting special mention. He discussed some common experimentation trends, and how organizations are embracing a shift left approach with chaos. And what better than validation of these thoughts from the experts at Gitlab! 

![image](https://user-images.githubusercontent.com/21166217/118845753-b1836080-b8e9-11eb-8f41-48be5edc0c86.png)

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Chaos Engineering. I&#39;m here for it. Shift left in CI/CD. 🙌<a href="https://twitter.com/hashtag/KubeCon?src=hash&amp;ref_src=twsrc%5Etfw">#KubeCon</a> <a href="https://twitter.com/hashtag/CloudNativeCon?src=hash&amp;ref_src=twsrc%5Etfw">#CloudNativeCon</a> <a href="https://t.co/YeS8YFJkgr">pic.twitter.com/YeS8YFJkgr</a></p>&mdash; Michael Friedrich, go SLO ... conf 📈🇦🇹 (@dnsmichi) <a href="https://twitter.com/dnsmichi/status/1389936157853618182?ref_src=twsrc%5Etfw">May 5, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

Next up was probably the [most interesting demo](https://youtu.be/btGFt5-37hs?t=740) (one that followed a nice intro/whiteboard session) involving litmus in the Kubecon. Saiyam (Civo) & Karthik (Verica) presented how one could leverage the GitOps & Event-triggered chaos features in the Litmus platform to test the sanity of the changes made to your application deployments on the cluster. It also had some cool takeaways on how you should approach chaos engineering & up your reliability game.

![image](https://user-images.githubusercontent.com/21166217/118845090-1be7d100-b8e9-11eb-9120-d58fcb35ee68.png)

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">The demo included -&gt; <a href="https://twitter.com/LitmusChaos?ref_src=twsrc%5Etfw">@LitmusChaos</a>, <a href="https://twitter.com/CivoCloud?ref_src=twsrc%5Etfw">@CivoCloud</a> Kubernetes, <a href="https://twitter.com/PrometheusIO?ref_src=twsrc%5Etfw">@PrometheusIO</a> and black box exporter <a href="https://twitter.com/grafana?ref_src=twsrc%5Etfw">@grafana</a>, <a href="https://twitter.com/fluxcd?ref_src=twsrc%5Etfw">@fluxcd</a>, <a href="https://twitter.com/github?ref_src=twsrc%5Etfw">@github</a> actions!<br><br>Repo -&gt; <a href="https://t.co/dHrXYESCd9">https://t.co/dHrXYESCd9</a> <a href="https://t.co/7Gd35fmmj1">https://t.co/7Gd35fmmj1</a></p>&mdash; Saiyam Pathak (@SaiyamPathak) <a href="https://twitter.com/SaiyamPathak/status/1390290962748903434?ref_src=twsrc%5Etfw">May 6, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> 

In between the various talks, we had the opportunity to hold the Office Hours (thanks a ton to the CNCF for organizing this) where community members, first time users got a chance to learn about the project & the advanced ones to probe us on the roadmap :). What better than waking up to messages like this from folks that attended the office hours: 

![image](https://user-images.githubusercontent.com/21166217/118845981-e099d200-b8e9-11eb-83f1-518af04a14aa.png)

<blockquote class="twitter-tweet"><p lang="en" dir="ltr"><a href="https://twitter.com/hashtag/Chaos?src=hash&amp;ref_src=twsrc%5Etfw">#Chaos</a> <a href="https://twitter.com/LitmusChaos?ref_src=twsrc%5Etfw">@LitmusChaos</a> was a big surprise for me in <a href="https://twitter.com/hashtag/kubeconEU?src=hash&amp;ref_src=twsrc%5Etfw">#kubeconEU</a>. They have an excellent solution for controlled and scheduled chaos validation in production environments for many services running on K8s. Great solution for Disaster Recovery and self healing tests</p>&mdash; Matheus Fidelis @ 127.0.0.1 (@fidelissauro) <a href="https://twitter.com/fidelissauro/status/1389564772866220033?ref_src=twsrc%5Etfw">May 4, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

Amidst all this, we had our SIG-Docs lead [@Divya_Mohan02](https://twitter.com/Divya_Mohan02) [participating](https://www.youtube.com/watch?v=445UZFpbG90&list=PLHgdNuGxrJt0ZHXZlIxDi6DTdfJbXGFo1&index=15) in the awesome DoKC Day (Data on Kubernetes Community), where she shared her contribution journey in LitmusChaos, what it means to break things intentionally & how folks can get involved with the project. 

![image](https://user-images.githubusercontent.com/21166217/118846472-5bfb8380-b8ea-11eb-9b37-f59720c37a94.png)

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">&quot;The art of intentionally breaking things&quot;=chaos engineering/the title of <a href="https://twitter.com/Divya_Mohan02?ref_src=twsrc%5Etfw">@Divya_Mohan02</a>&#39;s talk about her experience working with <a href="https://twitter.com/LitmusChaos?ref_src=twsrc%5Etfw">@LitmusChaos</a> <a href="https://t.co/T3BlkKqXEX">https://t.co/T3BlkKqXEX</a></p>&mdash; Data on K8s Community (@DoKcommunity) <a href="https://twitter.com/DoKcommunity/status/1390222135851950083?ref_src=twsrc%5Etfw">May 6, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> 

# Looking Ahead

While we feel chaos engineering & LitmusChaos project’s approach towards it has been validated, **there is much work to do & improve**. The impending Litmus 2.0 launch is expected to improve the experience of users along with a host of useful features. Having said that, What are the aspects you are most interested in seeing Litmus get better at, features you’d like to include or integrations you’d like to see? 

Feel free to get involved in these discussions on our slack channel or post your thoughts into the Github discussions ! 


---------------
Are you an SRE, developer, or a Kubernetes enthusiast? Does Chaos Engineering excite you? Join our community on [Slack](https://slack.litmuschaos.io/) For detailed discussions & regular updates On Chaos Engineering For Kubernetes.

Check out the LitmusChaos [GitHub repo](https://github.com/litmuschaos/litmus) and do share your feedback. Submit a pull request if you identify any necessary changes.