Update ADOPTERS.md with Litmus usage details

[ksatchit]

The LitmusChaos Community is working towards increasing adoption of chaos engineering practices within the Kubernetes world & is focused on collaboration with other cloud-native projects. One of the ways of tracking the project's reach is via an ADOPTERS list. The purpose of this issue is to get a list of organizations/individuals who are using Litmus to power their chaosengineering practice and also share broadly their usecases & reasons for choosing Litmus.

Please comment on this issue with details like:

• Applications/Workloads or Infra that are being subjected to chaos by Litmus
• Why was Litmus chosen & how it is helping you (a brief description on the usecase)
• Are you using it as part of devtest, CI/CD, in staging/pre-prod/prod or other
• If you would like your name (as standalone user) or organization name to be added to the Adopters.md, please provide a preferred contact handle like github id, twitter id, linkedin id, website etc.

This information will be used to create a PR on the ADOPTERS.md file, which you can approve. Alternatively, feel free to create a PR and reference this issue !

[divya-mohan0209]

• I am currently using LitmusChaos to demonstrate a POC for Chaos Engineering on Serverless Architecture.
• I shall be presenting this at the DevFest Siberia 2020.
• GitHub ID: divya-mohan0209, Twitter Handle: Divya_Mohan02

[barkardk]

I am using LitmusChaos as a part of our QA cycle at the moment to verify resiliency and catch bugs. For now it is only used in AWS EKS and Ec2 instances , we are expanding it to usage in Azure hopefully soon.
Litmus looked solid, easy to implement and most of all easy to customise.
gitHub id xkbarkar, Netapp Inc

[keerthisagar40]

• k8 pods hosted on both aws and azure .
• Needed a clean way to introduce anomolies in the system to figure out its behaviour , litmus was the one that was clean and easy to use
• using it part of QA cycle
• Akridata

[ishantanu]

• Currently working on using Litmus for introducing Chaos in Kubernetes clusters.
• I was looking for a cloud-native way of introducing Chaos and after going through the details and other options, Litmus was probably the best fit.
• Usage of Litmus is still in preliminary stages. A limited set of chaos experiments are used for testing resiliency. This will change in the future.
• GitHub ID - ishantanu

[xunholy]

Applications/Workloads or Infra that are being subjected to chaos by Litmus:

• Internal workload pods and storage resilience (OpenEBS); This is to test my built-in cluster resilience running whilst running on arm64 architecture and building confidence in the design and overall architecture.

Why was Litmus chosen & how it is helping you (a brief description on the usecase):

• I reviewed several chaos tools and felt that Litmus being associated with CNCF and being an open-source tool aligns with my own personal preference and values. It has a very active community and repository, and there was well-documented information that helped during the initial learning phases.

Are you using it as part of devtest, CI/CD, in staging/pre-prod/prod or other:

• I'm using it to run my RPi Kubernetes cluster which is my home cluster. This is running my personal production workloads.

If you would like your name (as standalone user) or organization name to be added to the Adopters.md, please provide a preferred contact handle like github id, twitter id, linkedin id, website etc:

• Github ORG https://github.com/raspbernetes & LinkedIn https://www.linkedin.com/in/michael-fornaro-5b756179/

[olegch]

Applications/Workloads or Infra that are being subjected to chaos by Litmus

• Kublr-provisioned Kubernetes clusters; we apply litmus chaos load to stress-test the clusters and identify the weak spots and components prone to failures under stress when customer applications stress the system

Why was Litmus chosen & how it is helping you (a brief description on the usecase)

• Litmus is well-documented, well-supported open source tool with a great community and development team. It is flexible and allows us to adjust the chaos tests any way we need.

Are you using it as part of devtest, CI/CD, in staging/pre-prod/prod or other

• This is currently used as a part of development testing and adhoc experiments, although we are working on including litmus chaos tests into our standard automated QA process

If you would like your name (as standalone user) or organization name to be added to the Adopters.md, please provide a preferred contact handle like github id, twitter id, linkedin id, website etc.

• Oleg Chunikhin, CTO, Kublr
  • https://github.com/olegch
  • https://twitter.com/olgch
  • https://www.linkedin.com/in/olegch/
• Organization: Kublr, https://kublr.com
  • https://github.com/kublr
  • https://twitter.com/kublr
  • https://www.linkedin.com/company/kublr/

[niebomin]

Please add VMware as adopter. Will add more description later. Use case is Chaos Engineering in CD.