Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #3294 from rajdas98/cp-2.2.0
Cherrypick from master to 2.2.0
- Loading branch information
Showing
51 changed files
with
2,004 additions
and
297 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
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,13 @@ | ||
CNF Test Suite | ||
--- | ||
|
||
The [CNF Test Suite](https://github.com/cncf/cnf-testsuite) is an open source test suite for Cloud Native Network Function (CNF) developers and network operators to evaluate how well a telecom service (a platform or network application, aka CNF) follows cloud native principles and best practices, like resilience. | ||
|
||
## Why do we use Litmus | ||
Subjecting the telecom services to chaos testing is useful in finding failure points and suggesting remediation steps toward improving resilience. Therefore, we chose LitmusChaos to create resilience tests in the CNF Test Suite. | ||
|
||
## How do we use Litmus | ||
By including LitmusChaos experiments in the CNF Test Suite's workload tests, we are able to run telecom services in resilience experiments including: **pod-network-duplication**, **pod-network-corruption**, **pod-io-stress**, **pod-memory-hog**, **pod-delete**, **disk-fill**, **pod-network-latency**, and more. This helps the end user see how their service behaves when exposed to common application failures. | ||
|
||
## Benefits in using Litmus | ||
The benefits we see in LitmusChaos are: it is part of the CNCF ecosystem, it is designed for Kubernetes workloads, it has a vibrant community and it is well maintained. |
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,32 @@ | ||
## **Pole Emploi** | ||
|
||
[Pole Emploi](https://www.pole-emploi.fr/accueil/) is the public employment service in France. | ||
Its roles are, on the one hand, to compensate job seekers and help them find a job, and on the other hand, to guide companies in their recruitment. | ||
In order to do that, Pôle emploi's agents are mobilized on a daily basis to anticipate trends, innovate and bring together key players and relays in the field. | ||
|
||
|
||
### **Why we explored litmus** | ||
|
||
With around 5.6 millions end-users, and applications that generate hudge traffic and datas, | ||
the resiliency of our apps and infrastructures is a must-have! | ||
|
||
- Litmus is OPEN SOURCE | ||
- Litmus is designed for Kubernetes | ||
- Litmus is easy to deploy ( helm chart ) | ||
- Litmus is extendable ( experiments libs, predefined workflows, private hubs ) | ||
|
||
|
||
### How we explored litmus | ||
|
||
We explored Litmus to validate and increase the resiliency of our private and public Kubernetes clouds. | ||
|
||
- Testing resiliency of Kubernetes Infrastructure Components | ||
- Testing resiliency of Public applications hosted on Kubernetes | ||
- Testing resiliency of Private applications hosted on Kubernetes | ||
|
||
|
||
### Benefits of litmus | ||
|
||
Litmus allowed us to identify and work on the observability, configuration, and high availability of certain components which were not resilient. | ||
|
||
With the history of experiences, the Reliability score system, and all the statistics on the chaos tests, using random recurring tests, litmus allows us to audit, over time, the resilience of our platforms, and to have a global vision of the state of it. |
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
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
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
Oops, something went wrong.