[DOC] Added 'CRs' as an acronym for 'custom resources' (#4226)
Signed-off-by: Mehmet Mustafa Guersul <mehmetgursul@gmail.com> Signed-off-by: Saranya Jena <saranya.jena@harness.io> Co-authored-by: Mehmet Mustafa Guersul <mehmetgursull@gmail.com> Co-authored-by: Saranya Jena <saranya.jena@harness.io>
This commit is contained in:
parent
4bdeea3a64
commit
0fd84b718f
|
@ -26,7 +26,7 @@ inducing chaos tests in a controlled way. Developers & SREs can practice Chaos E
|
|||
Chaos Engineering principles & community collaborated. It is 100% open source & a CNCF project.
|
||||
|
||||
LitmusChaos takes a cloud-native approach to create, manage and monitor chaos. The platform itself runs as a set of microservices and uses Kubernetes
|
||||
custom resources to define the chaos intent, as well as the steady state hypothesis.
|
||||
custom resources (CRs) to define the chaos intent, as well as the steady state hypothesis.
|
||||
|
||||
At a high-level, Litmus comprises of:
|
||||
|
||||
|
|
Loading…
Reference in New Issue