litmuschaos · ajeshbaby · Jun 14, 2022 · Jun 9, 2022 · Jun 9, 2022 · Jun 9, 2022
diff --git a/ADOPTERS.md b/ADOPTERS.md
@@ -20,6 +20,10 @@ The companies listed here conform to [CNCF's definition of end-users](https://gi
 |[Mercedes](https://www.mercedes-benz.com/)|Resiliency validation for applications|[Our Story](adopters/organizations/mercedes.md)|
 |[Orange](https://www.orange.com)|[Cloud Infra Resiliency](https://youtu.be/UOhjFbCrncw?list=PLBuYBMjBLBzHPuPsvdbJvKu1KxSowWDYl&t=186...a)|[Our Story](adopters/organizations/orange.md)|
 |[Pôle Emploi](https://www.pole-emploi.fr)|Chaos Engineering as part of SRE practice|[Our Story](adopters/organizations/pole_emploi.md)|
+|[iFood](https://www.ifood.com.br/)|Chaos Engineering for a Food Delivery Platform|[Our Story](adopters/organizations/ifood.md)|
+|[FIS](https://www.fisglobal.com/en/)|Larger SRE Transformation with Chaos Engineering|[Our Story](adopters/organizations/fis.md)|
+|[Adidas](https://adidas.com/)|Implementing Chaos Engineering as a practice at Adidas|[Our Story](adopters/organizations/adidas.md)|
+|[Cyren](https://www.cyren.com/)|Implementing Chaos Engineering as a practice at Cyren|[Our Story](https://www.infoq.com/articles/chaos-engineering-cloud-native/)|
 
 ### Cloud-Native Vendors
 
@@ -36,6 +40,7 @@ devops/reliability pipelines (such as for customer portals/websites etc.,) withi
 |[RedHat](https://www.redhat.com/en)|[RedHat Openshift Virtualization Maturity](https://www.youtube.com/watch?v=VITGHJ47gx8&list=PLBuYBMjBLBzHPuPsvdbJvKu1KxSowWDYl&index=7)|[Our Story](adopters/organizations/redhat.md)|
 |[VMWare](https://www.vmware.com/)|Chaos Engineering in CD|[Our Story](adopters/organizations/vmware.md)|
 |[Zebrium](https://www.zebrium.com?utm_source=github&utm_campaign=litmuschaos_repo)|[Zebrium K8s Chaos Project](https://github.com/zebrium/zebrium-kubernetes-demo)|[Our Story](adopters/organizations/zebrium.md)|
+|[Container Solutions](https://www.container-solutions.com/)|Building Chaos Engineering for E-Commerce Customers|[Our Story](adopters/organizations/containersolutions.md)|
 
 ### Cloud-Native Solutions & Service Providers
 

diff --git a/COMMERCIAL_SUPPORT.md b/COMMERCIAL_SUPPORT.md
@@ -5,4 +5,4 @@ If you are a commercial support provider for LitmusChaos and wish to add your co
 
 The list is provided in alphabetical order.
 
-- [ChaosNative](https://www.chaosnative.com/)
+- [Harness](https://harness.io/products/chaos-engineering)
diff --git a/TRAINING_AND_COURSES.md b/TRAINING_AND_COURSES.md
@@ -0,0 +1,8 @@
+# LitmusChaos Training and Courses
+
+Here is a list of training and courses related to LitmusChaos available out there. LitmusChaos is a CNCF project which does not endorse any particular course. 
+If you have created a training or course for LitmusChaos and wish to add the same, please raise a PR against this document.
+
+
+- [Harness Chaos Engineering Practitioner](https://university.harness.io/path/harness-chaos-engineering-practitioner)
+- [Configuring Kubernetes for Reliability with LitmusChaos](https://www.udemy.com/course/configuring-kubernetes-for-reliability-with-litmuschaos/)
diff --git a/adopters/organizations/adidas.md b/adopters/organizations/adidas.md
@@ -0,0 +1,29 @@
+## Adidas
+[Adidas](https://adidas.com) is a German multinational corporation, founded and headquartered in Herzogenaurach, Bavaria, that designs and manufactures shoes, clothing and accessories. 
+
+
+## Why do we use Litmus.  
+
+In adidas, we started months ago with a new initiative about how to implement chaos engineering practices in order to provide the engineering teams a guide and tools about how to test the resilience of the applications through chaos engineering. With this goal in mind, we started to define some best practices and processes to be shared with our engineering team, and we started to evaluate a few tools.
+
+After an evaluation of different tools, we decided to go ahead with Litmus Chaos.
+
+## How are we using Litmus chaos:
+Applications/Workloads or Infra that are being subjected to chaos by Litmus
+
+- Litmus chaos will be provided by our platform team as part of their services. It will be running on kubernetes and will be available for engineering teams.
+- Experiments, like pod deletion, network latency or packetloss, applied between functional dependencies like checkout & Payments, login, order creation...
+- Not applied in production yet.
+
+## Why was Litmus chosen & How it is helping you 
+We defined a set of priorities (with different value) and stoppers, we analyzed the tooling and selected the most valued one:
+
+- Prio 1 & Stoppers if not: Full detailed documentation in English available, API / Shared Libraries, Control Injecting Failure, Permissions scope isolated, Authorization, chaos Scenarios - Parallel, works with: Kuberentes, OpenSource
+- Prio 2: Installation and Management, Metrics / Reporting, Halt attack, Automatic rollback, High/admin permissions on the node, Chaos scenarios as code, chaos attacks - Serial, Custom or Specialized Attacks, Custom or Specialized Scenarios, Works with: AWS
+- Prio 3: Access to the logs, Scheduling attacks, Health Checks, Application Attacks, Target Randomization, Network Attacks, VMs Attacks, Public API, Web UI
+
+## How do we use Litmus
+- Staging/pre-prod
+- Planned to go to production and through CI/CD pipelines.
+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.
+
diff --git a/adopters/organizations/containersolutions.md b/adopters/organizations/containersolutions.md
@@ -0,0 +1,12 @@
+## Container Solutions
+[Container Solutions](https://www.container-solutions.com/) We bring culture, strategy, and technology together —to make sure your Cloud Native transformation is done right.
+
+## How do we use Litmus
+We have used Litmus to build out Chaos Engineering platforms with some of our large E-Commerce customers to improve resilience for big sales periods such as Black Friday.
+
+We looked into quite a few tools, and Litmus provided us with the flexibility we needed, whilst bootstrapping many of the components we would have to write ourselves.
+
+We also used Litmus Chaos experiments when discussing some of our customer's architecture constraints, and showing them real world cases of how to make Kubernetes more resilient.
+
+One concrete use case was our customer wanting to build a cluster per app, whilst we wanted to build bigger clusters for easier management. We would use Litmus to show what application failure looks like on one part of the cluster, and show global resilience in their cluster when this happens.
+The Litmus community and *product have been a great addition to our tool stack, and provided many benefits for us.
diff --git a/adopters/organizations/fis.md b/adopters/organizations/fis.md
@@ -0,0 +1,20 @@
+## FIS
+[FIS](https://www.fisglobal.com/) is an American multinational corporation which offers a wide range of financial products and services.
+
+## Why do we use Litmus.  
+We at FIS Global, have been embarking on to larger SRE program to transform platform teams from purely operations focused to bring in SRE/Automation culture and mindset. As part of that larger effort, Chaos/Resiliency Engineering is identified as key program to improve stability and availability thus improve overall reliability of applications across organization and provide superior customer experience. We have chosen Litmus as a Chaos Engineering Tool because, It
+
+Fulfills all of resiliency testing requirements
+Has good and responsive community
+Has good documentation
+is built on loosely coupled architecture
+Has nice dashboard features
+Exposes APIs to integrate with CI/CD pipelines
+
+## Where we are using Litmus
+
+Currently, using in Applications/Workloads but idea is to expand to Infrastructure, e.g. using network latency to identify and understand resiliency of upstream application/component when downstream application/component is slow, Use Pod delete under production load to understand the application's ability to self heal.
+Simulate experiments using Litmus to understand utilization of JVM's key resources such as thread pool, connection pool, heap memory etc
+Kafka Resiliency : Kafka itself is a complex distributed architecture solution, planning to use Litmus network and memory hog experiments to simulate latency between Producer and Broker, Consumer and Broker, Leader and Follower, and also trying to understand how cluster behaves under Memory and CPU pressure.
+Integrate Litmus with CI/CD over APIs so that Chaos Testing can be autonomous
+
diff --git a/adopters/organizations/ifood.md b/adopters/organizations/ifood.md
@@ -0,0 +1,6 @@
+## iFood
+[iFood](https://ifood.com.br) is a Brazilian online food ordering and food delivery platform. It operates mainly in Brazil and Mexico, after it merged its businesses in Argentina and Colombia with rival PedidosYa.
+
+## How are we using Litmus
+We have been using Litmus 2.X at iFood for a couple of months, replacing chaostoolkit as it provides a wider range of experiments out-of-the-box. We've started using it to validate the fallback mechanisms of critical services monthly. Right now, we are expanding its usage to go further and inject failures to drop access to databases, redis, Kafka and AWS services and learn from it and take some countermeasures to improve the critical services.
+I hope Litmus to become the de-facto tool to implement Chaos Engineering in a simple manner.