Skip to content

Commit

Permalink
Adding Adopters (litmuschaos#3979)
Browse files Browse the repository at this point in the history
* Create infracloud.md

* Update infracloud.md

* Create apisix.md

* Update ADOPTERS.md

Signed-off-by: SohamRatnaparkhi <[email protected]>
  • Loading branch information
prithvi1307 authored and SohamRatnaparkhi committed Jun 30, 2023
1 parent 5c8666a commit b4db124
Show file tree
Hide file tree
Showing 3 changed files with 42 additions and 0 deletions.
3 changes: 3 additions & 0 deletions ADOPTERS.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,8 @@ devops/reliability pipelines (such as for customer portals/websites etc.,) withi
|[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)|
|[Infracloud Technologies](https://www.infracloud.io/)|Developing Resiliency Framework at Infracloud|[Our Story](adopters/organizations/infracloud.md)|


### Cloud-Native Solutions & Service Providers

Expand Down Expand Up @@ -72,5 +74,6 @@ existing functions.
|[Red Hat](https://www.redhat.com/en)|[Chaos Engineering with Kraken](https://github.com/cloud-bulldozer/kraken)|[Our Story](adopters/organizations/redhat_kraken.md)|
|[Iter8](https://iter8.tools)|[SLO validation with chaos injection](https://iter8.tools/0.7/tutorials/deployments/slo-validation-chaos/)|To Be Added|
|[CNF Test Suite](https://github.com/cncf/cnf-testsuite)|To validate the resilience of Cloud Native Network Functions (CNFs)|[Our Story](adopters/organizations/cnftestsuite.md)|
|[APACHE APISIX](https://apisix.apache.org/)|Practicing Chaos Engineering using Litmus in the Apache APISIX Ingress.|[Our Story](adopters/organizations/apisix.md)|


16 changes: 16 additions & 0 deletions adopters/organizations/apisix.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# APISIX Apache

Developed and donated by API7.ai, Apache APISIX is an open source, dynamic, scalable, and high-performance cloud native API gateway for all your APIs and microservices. It is a top-level project of the Apache Software Foundation.

You can use APISIX API Gateway as a traffic entrance to process all business data. It offers features including dynamic routing, dynamic upstream, dynamic certificates, A/B testing, canary release, blue-green deployment, limit rate, defense against malicious attacks, metrics, monitoring alarms, service observability, service governance, and more.




## How do we use Litmus
We practice chaos engineering using Litmus in the Apache APISIX Ingress.

Litmus also helped us find hidden bugs.

Project website: https://apisix.apache.org/
This is the text version of my online sharing content. https://dev.to/apisix/building-a-more-robust-apache-apisix-ingress-controller-with-litmus-chaos-3ldn
23 changes: 23 additions & 0 deletions adopters/organizations/infracloud.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# Infracloud Technologies

InfraCloud Technologies is a Kubernetes focused B2B Open Source Cloud Native Computing company which has been building products, services, and solutions to modernize applications and infrastructure.

InfraCloud was one of the first Kubernetes partners and have been contributing to the open source community around cloud-native technologies. It has been growing almost 100% for last few years consistently.

Company website: https://www.infracloud.io/
Company GitHub: https://github.com/infracloudio

## Why Do We Use Litmus:

At InfraCloud, we are using Litmus to develop Resiliency Frameworks.
To simulate various Chaos scenarios using fault injection templates provided by Litmus. Litmus also helps to incorporate custom fault templates developed using AWS SSM documents.

## How do we use Litmus.
Currently, we have tested with different kind of scenarios including faults like pod deletion, network latency, resource stressing, network partitioning in databases, and many more.

## Benefits in using Litmus.

Easy deployment.
Easy Fault injection.
Custom Grading for experiments
SSM integration helps to inject fault in both EKS and external AWS components.

0 comments on commit b4db124

Please sign in to comment.