-
Notifications
You must be signed in to change notification settings - Fork 697
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
* Adding Kublr as adopter reference #2191
- Loading branch information
Showing
2 changed files
with
20 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
## Kublr | ||
|
||
[Kublr](https://kublr.com/) is an Enterprise-ready orchestration platform to centrally deploy, run, and manage Kubernetes clusters across all of your environments with a comprehensive container orchestration platform that finally delivers on the Kubernetes promise. Optimized for large enterprises, Kublr is designed to provide multi-cluster deployments and observability. We made it easy, so your team can focus on what really matters: innovation and value generation. | ||
|
||
### **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 | ||
|