added chaos-operator and chaos-runner flow diagrams to chaos execution plane and centered monitoring diagrams (#129)

Signed-off-by: neelanjan00 <[email protected]>

Author: Neelanjan Manna

website/docs/architecture/chaos-execution-plane.md

@@ -33,10 +33,18 @@ Litmus Backend Execution Infrastructure components orchestrate the execution of
 
 4. **Chaos Operator:** A Kubernetes custom-controller that manages the lifecycle of certain resources or applications intending to validate their "desired state". It helps reconcile the state of the ChaosEngine by performing specific actions upon CRUD of the ChaosEngine. It also defines a secondary resource (the ChaosEngine Runner pod), which is created & managed by it to implement the reconcile functions.
 
+<div style={{textAlign: 'center'}}>
+  <img src={require("../assets/chaos-execution-plane-chaos-operator.png").default} alt="Chaos Operator" />
+</div>
+
 5. **ChaosResult CR:** Holds the results of a chaos experiment, such as ChaosEngine reference, Experiment State, Verdict of the experiment (on completion), salient application/result attributes. It also acts as a source for metrics collection for observability.
 
 6. **Chaos Runner:** Acts as a bridge between the Chaos Operator and Chaos Experiments. It is a lifecycle manager for the chaos experiments that creates Experiment Jobs for the execution of experiment business logic and monitors the experiment pods (jobs) until completion.
 
+<div style={{textAlign: 'center'}}>
+  <img src={require("../assets/chaos-execution-plane-chaos-runner.png").default} alt="Chaos Runner" />
+</div>
+
 7. **Experiment Jobs:** Refers to the pods that execute the experiment logic. One experiment pod is created per chaos experiment in the workflow.
 
 ## Standard Chaos Execution Plane Flow

website/docs/architecture/chaos-observability-flow-monitoring.md

@@ -12,7 +12,9 @@ Monitoring is a key part to effectively watch and understand the state of the sy
 
 ## Metrics Monitoring
 
-<img src={require("../assets/chaos-observability-flow-metrics.png").default} alt="Chaos Observability Flow Metrics" />
+<div style={{textAlign: 'center'}}>
+  <img src={require("../assets/chaos-observability-flow-metrics.png").default} alt="Chaos Observability Flow Metrics" />
+</div>
 
 Metrics Monitoring enables the users to monitor the chaos metrics generated during chaos injection, which is exported by the chaos exporter to be consumed as time-series information.
 
@@ -25,7 +27,9 @@ Metrics Monitoring enables the users to monitor the chaos metrics generated duri
 
 ## Events Monitoring
 
-<img src={require("../assets/chaos-observability-flow-events.png").default} alt="Chaos Observability Flow Events" />
+<div style={{textAlign: 'center'}}>
+  <img src={require("../assets/chaos-observability-flow-events.png").default} alt="Chaos Observability Flow Events" />
+</div>
 
 Events Monitoring enables the users to monitor the Kubernetes events that are created as part of the orchestration of chaos injection by Litmus. These events occur through different points in the lifetime of a Chaos Experiment's execution to accomplish.
 

website/docs/assets/chaos-execution-plane-chaos-operator.png

@@ -33,10 +33,18 @@ Litmus Backend Execution Infrastructure components orchestrate the execution of
 
 4. **Chaos Operator:** A Kubernetes custom-controller that manages the lifecycle of certain resources or applications intending to validate their "desired state". It helps reconcile the state of the ChaosEngine by performing specific actions upon CRUD of the ChaosEngine. It also defines a secondary resource (the ChaosEngine Runner pod), which is created & managed by it to implement the reconcile functions.
 
+<div style={{textAlign: 'center'}}>
+  <img src={require("../assets/chaos-execution-plane-chaos-operator.png").default} alt="Chaos Operator" />
+</div>
+
 5. **ChaosResult CR:** Holds the results of a chaos experiment, such as ChaosEngine reference, Experiment State, Verdict of the experiment (on completion), salient application/result attributes. It also acts as a source for metrics collection for observability.
 
 6. **Chaos Runner:** Acts as a bridge between the Chaos Operator and Chaos Experiments. It is a lifecycle manager for the chaos experiments that creates Experiment Jobs for the execution of experiment business logic and monitors the experiment pods (jobs) until completion.
 
+<div style={{textAlign: 'center'}}>
+  <img src={require("../assets/chaos-execution-plane-chaos-runner.png").default} alt="Chaos Runner" />
+</div>
+
 7. **Experiment Jobs:** Refers to the pods that execute the experiment logic. One experiment pod is created per chaos experiment in the workflow.
 
 ## Standard Chaos Execution Plane Flow

website/docs/assets/chaos-execution-plane-chaos-runner.png

@@ -12,7 +12,9 @@ Monitoring is a key part to effectively watch and understand the state of the sy
 
 ## Metrics Monitoring
 
-<img src={require("../assets/chaos-observability-flow-metrics.png").default} alt="Chaos Observability Flow Metrics" />
+<div style={{textAlign: 'center'}}>
+  <img src={require("../assets/chaos-observability-flow-metrics.png").default} alt="Chaos Observability Flow Metrics" />
+</div>
 
 Metrics Monitoring enables the users to monitor the chaos metrics generated during chaos injection, which is exported by the chaos exporter to be consumed as time-series information.
 
@@ -25,7 +27,9 @@ Metrics Monitoring enables the users to monitor the chaos metrics generated duri
 
 ## Events Monitoring
 
-<img src={require("../assets/chaos-observability-flow-events.png").default} alt="Chaos Observability Flow Events" />
+<div style={{textAlign: 'center'}}>
+  <img src={require("../assets/chaos-observability-flow-events.png").default} alt="Chaos Observability Flow Events" />
+</div>
 
 Events Monitoring enables the users to monitor the Kubernetes events that are created as part of the orchestration of chaos injection by Litmus. These events occur through different points in the lifetime of a Chaos Experiment's execution to accomplish.