Litmus Docs Fixes [Architecture Diagrams, Missing Operator and Runner Diagrams, and GitOps Clarification] (#150)

* updated background color of architecture diagram, added operator and runner flow charts to v2.1 and v2.2 docs

Signed-off-by: neelanjan00 <neelanjan@chaosnative.com>

* added note for gitops behaviour when a workflow is pushed to the git repo

Signed-off-by: neelanjan00 <neelanjan@chaosnative.com>

* updated note for gitops behaviour

Signed-off-by: neelanjan00 <neelanjan@chaosnative.com>

* updated for v2.3 and v2.4

Signed-off-by: neelanjan00 <neelanjan@chaosnative.com>

* update note blocks

Signed-off-by: neelanjan00 <neelanjan@chaosnative.com>

website/docs/user-guides/gitops-configuration.md

@@ -17,8 +17,6 @@ GitOps enables you to configure a single source of truth for your chaos workflow
 
 ## Steps to configure GitOps
 
-
-
 - Setup a git repository, so that the ChaosCenter can sync with it, and push all the workflows in that repository.
 - The git repo can be public or private but for authorization, you have to provide an access token or any other mode of authentication.
 - Login into ChaosCenter, go to `GitOps` tab under `Settings`.
@@ -37,8 +35,11 @@ GitOps enables you to configure a single source of truth for your chaos workflow
 - Some metadata will be pushed to your repository, that is the projectID of your project.
 - Now whenever you schedule a workflow, it will automatically be pushed to your repository. And that repository will be the single source of truth.
 
-## Steps to configure Event-Triggered Chaos Injection
+:::note
+It is also possible to account for the workflows that are created and pushed to the git repository directly, after configuring GitOps. In this case, if the workflow is a single run workflow, then it starts executing as soon as it is pushed to the repository. Alternatively, if the workflow is a scheduled workflow, then it executes as per the defined schedule. On the other hand, updating an existing workflow present in the git repository will not execute the workflow but only sync the workflow resource definition with the ChaosCenter, if applicable.
+:::
 
+## Steps to configure Event-Triggered Chaos Injection
 
 - Once the workflow is pushed to your repository, you’ll notice every workflow has a `workflow_id`. You can get this from the workflow YAML file. You need to copy the id and annotate the target application so that if there’s any change in the application, gitops will sync the workflow using this workflow_id and run it on your target application. You can use the following command:
 

website/package-lock.json

@@ -3372,24 +3372,16 @@
 			}
 		},
 		"node_modules/algoliasearch-helper": {
-			"version": "3.5.4",
-			"resolved": "https://registry.npmjs.org/algoliasearch-helper/-/algoliasearch-helper-3.5.4.tgz",
-			"integrity": "sha512-t+FLhXYnPZiwjYe5ExyN962HQY8mi3KwRju3Lyf6OBgtRdx30d6mqvtClXf5NeBihH45Xzj6t4Y5YyvAI432XA==",
+			"version": "3.7.0",
+			"resolved": "https://registry.npmjs.org/algoliasearch-helper/-/algoliasearch-helper-3.7.0.tgz",
+			"integrity": "sha512-XJ3QfERBLfeVCyTVx80gon7r3/rgm/CE8Ha1H7cbablRe/X7SfYQ14g/eO+MhjVKIQp+gy9oC6G5ilmLwS1k6w==",
 			"dependencies": {
-				"events": "^1.1.1"
+				"@algolia/events": "^4.0.1"
 			},
 			"peerDependencies": {
 				"algoliasearch": ">= 3.1 < 5"
 			}
 		},
-		"node_modules/algoliasearch-helper/node_modules/events": {
-			"version": "1.1.1",
-			"resolved": "https://registry.npmjs.org/events/-/events-1.1.1.tgz",
-			"integrity": "sha1-nr23Y1rQmccNzEwqH1AEKI6L2SQ=",
-			"engines": {
-				"node": ">=0.4.x"
-			}
-		},
 		"node_modules/alphanum-sort": {
 			"version": "1.0.2",
 			"resolved": "https://registry.npmjs.org/alphanum-sort/-/alphanum-sort-1.0.2.tgz",
@@ -3460,10 +3452,10 @@
 				"url": "https://github.com/sponsors/sindresorhus"
 			}
 		},
-		"node_modules/ansi-html": {
-			"version": "0.0.7",
-			"resolved": "https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz",
-			"integrity": "sha1-gTWEAhliqenm/QOflA0S9WynhZ4=",
+		"node_modules/ansi-html-community": {
+			"version": "0.0.8",
+			"resolved": "https://registry.npmjs.org/ansi-html-community/-/ansi-html-community-0.0.8.tgz",
+			"integrity": "sha512-1APHAyr3+PCamwNw3bXCPp4HFLONZt/yIH0sZp0/469KWNTEy+qN5jQ3GVX6DMZ1UXAi34yVwtTeaG/HpBuuzw==",
 			"engines": [
 				"node >= 0.8.0"
 			],
@@ -3637,11 +3629,11 @@
 			}
 		},
 		"node_modules/axios": {
-			"version": "0.21.1",
-			"resolved": "https://registry.npmjs.org/axios/-/axios-0.21.1.tgz",
-			"integrity": "sha512-dKQiRHxGD9PPRIUNIWvZhPTPpl1rf/OxTYKsqKUDjBwYylTvV7SjSHJb9ratfyzM6wCdLCOYLzs73qpg5c4iGA==",
+			"version": "0.21.4",
+			"resolved": "https://registry.npmjs.org/axios/-/axios-0.21.4.tgz",
+			"integrity": "sha512-ut5vewkiu8jjGBdqpM44XxjuCjq9LAKeHVmoVfHVzy8eHgxxq8SbAVQNovDA8mVi05kP0Ea/n/UzcSHcTJQfNg==",
 			"dependencies": {
-				"follow-redirects": "^1.10.0"
+				"follow-redirects": "^1.14.0"
 			}
 		},
 		"node_modules/babel-loader": {
@@ -9117,9 +9109,9 @@
 			"integrity": "sha1-y480xTIT2JVyP8urkH6UIq28r7E="
 		},
 		"node_modules/nth-check": {
-			"version": "2.0.0",
-			"resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz",
-			"integrity": "sha512-i4sc/Kj8htBrAiH1viZ0TgU8Y5XqCaV/FziYK6TBczxmeKm3AEFWqqF3195yKudrarqy7Zu80Ra5dobFjn9X/Q==",
+			"version": "2.0.1",
+			"resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.1.tgz",
+			"integrity": "sha512-it1vE95zF6dTT9lBsYbxvqh0Soy4SPowchj0UBGj/V6cTPnXXtQOPUbhZ6CmGzAD/rW22LQK6E96pcdJXk4A4w==",
 			"dependencies": {
 				"boolbase": "^1.0.0"
 			},
@@ -10377,9 +10369,12 @@
 			}
 		},
 		"node_modules/prismjs": {
-			"version": "1.24.1",
-			"resolved": "https://registry.npmjs.org/prismjs/-/prismjs-1.24.1.tgz",
-			"integrity": "sha512-mNPsedLuk90RVJioIky8ANZEwYm5w9LcvCXrxHlwf4fNVSn8jEipMybMkWUyyF0JhnC+C4VcOVSBuHRKs1L5Ow=="
+			"version": "1.26.0",
+			"resolved": "https://registry.npmjs.org/prismjs/-/prismjs-1.26.0.tgz",
+			"integrity": "sha512-HUoH9C5Z3jKkl3UunCyiD5jwk0+Hz0fIgQ2nbwU2Oo/ceuTAQAg+pPVnfdt2TJWRVLcxKh9iuoYDUSc8clb5UQ==",
+			"engines": {
+				"node": ">=6"
+			}
 		},
 		"node_modules/process-nextick-args": {
 			"version": "2.0.1",
@@ -12560,9 +12555,9 @@
 			}
 		},
 		"node_modules/strip-ansi/node_modules/ansi-regex": {
-			"version": "5.0.0",
-			"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz",
-			"integrity": "sha512-bY6fj56OUQ0hU1KjFNDQuJFezqKdrAyFdIevADiqrWHwSlbmBNMHp5ak2f40Pm8JTFyM2mqxkG6ngkHO11f/lg==",
+			"version": "5.0.1",
+			"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
+			"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
 			"engines": {
 				"node": ">=8"
 			}
@@ -13325,9 +13320,9 @@
 			}
 		},
 		"node_modules/url-parse": {
-			"version": "1.5.1",
-			"resolved": "https://registry.npmjs.org/url-parse/-/url-parse-1.5.1.tgz",
-			"integrity": "sha512-HOfCOUJt7iSYzEx/UqgtwKRMC6EU91NFhsCHMv9oM03VJcVo2Qrp8T8kI9D7amFf1cu+/3CEhgb3rF9zL7k85Q==",
+			"version": "1.5.4",
+			"resolved": "https://registry.npmjs.org/url-parse/-/url-parse-1.5.4.tgz",
+			"integrity": "sha512-ITeAByWWoqutFClc/lRZnFplgXgEZr3WJ6XngMM/N9DMIm4K8zXPCZ1Jdu0rERwO84w1WC5wkle2ubwTA4NTBg==",
 			"dependencies": {
 				"querystringify": "^2.1.1",
 				"requires-port": "^1.0.0"
@@ -13693,11 +13688,11 @@
 			}
 		},
 		"node_modules/webpack-dev-server": {
-			"version": "3.11.2",
-			"resolved": "https://registry.npmjs.org/webpack-dev-server/-/webpack-dev-server-3.11.2.tgz",
-			"integrity": "sha512-A80BkuHRQfCiNtGBS1EMf2ChTUs0x+B3wGDFmOeT4rmJOHhHTCH2naNxIHhmkr0/UillP4U3yeIyv1pNp+QDLQ==",
+			"version": "3.11.3",
+			"resolved": "https://registry.npmjs.org/webpack-dev-server/-/webpack-dev-server-3.11.3.tgz",
+			"integrity": "sha512-3x31rjbEQWKMNzacUZRE6wXvUFuGpH7vr0lIEbYpMAG9BOxi0928QU1BBswOAP3kg3H1O4hiS+sq4YyAn6ANnA==",
 			"dependencies": {
-				"ansi-html": "0.0.7",
+				"ansi-html-community": "0.0.8",
 				"bonjour": "^3.5.0",
 				"chokidar": "^2.1.8",
 				"compression": "^1.7.4",
@@ -14644,6 +14639,11 @@
 				"@algolia/transporter": "4.10.3"
 			}
 		},
+		"@algolia/events": {
+			"version": "4.0.1",
+			"resolved": "https://registry.npmjs.org/@algolia/events/-/events-4.0.1.tgz",
+			"integrity": "sha512-FQzvOCgoFXAbf5Y6mYozw2aj5KCJoA3m4heImceldzPSMbdyS4atVjJzXKMsfX3wnZTFYwkkt8/z8UesLHlSBQ=="
+		},
 		"@algolia/logger-common": {
 			"version": "4.10.3",
 			"resolved": "https://registry.npmjs.org/@algolia/logger-common/-/logger-common-4.10.3.tgz",
@@ -17022,18 +17022,11 @@
 			}
 		},
 		"algoliasearch-helper": {
-			"version": "3.5.4",
-			"resolved": "https://registry.npmjs.org/algoliasearch-helper/-/algoliasearch-helper-3.5.4.tgz",
-			"integrity": "sha512-t+FLhXYnPZiwjYe5ExyN962HQY8mi3KwRju3Lyf6OBgtRdx30d6mqvtClXf5NeBihH45Xzj6t4Y5YyvAI432XA==",
+			"version": "3.7.0",
+			"resolved": "https://registry.npmjs.org/algoliasearch-helper/-/algoliasearch-helper-3.7.0.tgz",
+			"integrity": "sha512-XJ3QfERBLfeVCyTVx80gon7r3/rgm/CE8Ha1H7cbablRe/X7SfYQ14g/eO+MhjVKIQp+gy9oC6G5ilmLwS1k6w==",
 			"requires": {
-				"events": "^1.1.1"
-			},
-			"dependencies": {
-				"events": {
-					"version": "1.1.1",
-					"resolved": "https://registry.npmjs.org/events/-/events-1.1.1.tgz",
-					"integrity": "sha1-nr23Y1rQmccNzEwqH1AEKI6L2SQ="
-				}
+				"@algolia/events": "^4.0.1"
 			}
 		},
 		"alphanum-sort": {
@@ -17042,31 +17035,11 @@
 			"integrity": "sha1-l6ERlkmyEa0zaR2fn0hqjsn74KM="
 		},
 		"ansi-align": {
-			"version": "3.0.0",
-			"resolved": "https://registry.npmjs.org/ansi-align/-/ansi-align-3.0.0.tgz",
-			"integrity": "sha512-ZpClVKqXN3RGBmKibdfWzqCY4lnjEuoNzU5T0oEFpfd/z5qJHVarukridD4juLO2FXMiwUQxr9WqQtaYa8XRYw==",
+			"version": "3.0.1",
+			"resolved": "https://registry.npmjs.org/ansi-align/-/ansi-align-3.0.1.tgz",
+			"integrity": "sha512-IOfwwBF5iczOjp/WeY4YxyjqAFMQoZufdQWDd19SEExbVLNXqvpzSJ/M7Za4/sCPmQ0+GRquoA7bGcINcxew6w==",
 			"requires": {
-				"string-width": "^3.0.0"
-			},
-			"dependencies": {
-				"string-width": {
-					"version": "3.1.0",
-					"resolved": "https://registry.npmjs.org/string-width/-/string-width-3.1.0.tgz",
-					"integrity": "sha512-vafcv6KjVZKSgz06oM/H6GDBrAtz8vdhQakGjFIvNrHA6y3HCF1CInLy+QLq8dTJPQ1b+KDUqDFctkdRW44e1w==",
-					"requires": {
-						"emoji-regex": "^7.0.1",
-						"is-fullwidth-code-point": "^2.0.0",
-						"strip-ansi": "^5.1.0"
-					}
-				},
-				"strip-ansi": {
-					"version": "5.2.0",
-					"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-5.2.0.tgz",
-					"integrity": "sha512-DuRs1gKbBqsMKIZlrffwlug8MHkcnpjs5VPmL1PAh+mA30U0DTotfDZ0d2UUsXpPmPmMMJ6W773MaA3J+lbiWA==",
-					"requires": {
-						"ansi-regex": "^4.1.0"
-					}
-				}
+				"string-width": "^4.1.0"
 			}
 		},
 		"ansi-colors": {
@@ -17089,10 +17062,10 @@
 				}
 			}
 		},
-		"ansi-html": {
-			"version": "0.0.7",
-			"resolved": "https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz",
-			"integrity": "sha1-gTWEAhliqenm/QOflA0S9WynhZ4="
+		"ansi-html-community": {
+			"version": "0.0.8",
+			"resolved": "https://registry.npmjs.org/ansi-html-community/-/ansi-html-community-0.0.8.tgz",
+			"integrity": "sha512-1APHAyr3+PCamwNw3bXCPp4HFLONZt/yIH0sZp0/469KWNTEy+qN5jQ3GVX6DMZ1UXAi34yVwtTeaG/HpBuuzw=="
 		},
 		"ansi-regex": {
 			"version": "4.1.0",
@@ -17211,11 +17184,11 @@
 			}
 		},
 		"axios": {
-			"version": "0.21.1",
-			"resolved": "https://registry.npmjs.org/axios/-/axios-0.21.1.tgz",
-			"integrity": "sha512-dKQiRHxGD9PPRIUNIWvZhPTPpl1rf/OxTYKsqKUDjBwYylTvV7SjSHJb9ratfyzM6wCdLCOYLzs73qpg5c4iGA==",
+			"version": "0.21.4",
+			"resolved": "https://registry.npmjs.org/axios/-/axios-0.21.4.tgz",
+			"integrity": "sha512-ut5vewkiu8jjGBdqpM44XxjuCjq9LAKeHVmoVfHVzy8eHgxxq8SbAVQNovDA8mVi05kP0Ea/n/UzcSHcTJQfNg==",
 			"requires": {
-				"follow-redirects": "^1.10.0"
+				"follow-redirects": "^1.14.0"
 			}
 		},
 		"babel-loader": {
@@ -21388,9 +21361,9 @@
 			"integrity": "sha1-y480xTIT2JVyP8urkH6UIq28r7E="
 		},
 		"nth-check": {
-			"version": "2.0.0",
-			"resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz",
-			"integrity": "sha512-i4sc/Kj8htBrAiH1viZ0TgU8Y5XqCaV/FziYK6TBczxmeKm3AEFWqqF3195yKudrarqy7Zu80Ra5dobFjn9X/Q==",
+			"version": "2.0.1",
+			"resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.1.tgz",
+			"integrity": "sha512-it1vE95zF6dTT9lBsYbxvqh0Soy4SPowchj0UBGj/V6cTPnXXtQOPUbhZ6CmGzAD/rW22LQK6E96pcdJXk4A4w==",
 			"requires": {
 				"boolbase": "^1.0.0"
 			}
@@ -22226,9 +22199,9 @@
 			"requires": {}
 		},
 		"prismjs": {
-			"version": "1.24.1",
-			"resolved": "https://registry.npmjs.org/prismjs/-/prismjs-1.24.1.tgz",
-			"integrity": "sha512-mNPsedLuk90RVJioIky8ANZEwYm5w9LcvCXrxHlwf4fNVSn8jEipMybMkWUyyF0JhnC+C4VcOVSBuHRKs1L5Ow=="
+			"version": "1.26.0",
+			"resolved": "https://registry.npmjs.org/prismjs/-/prismjs-1.26.0.tgz",
+			"integrity": "sha512-HUoH9C5Z3jKkl3UunCyiD5jwk0+Hz0fIgQ2nbwU2Oo/ceuTAQAg+pPVnfdt2TJWRVLcxKh9iuoYDUSc8clb5UQ=="
 		},
 		"process-nextick-args": {
 			"version": "2.0.1",
@@ -23946,9 +23919,9 @@
 			},
 			"dependencies": {
 				"ansi-regex": {
-					"version": "5.0.0",
-					"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz",
-					"integrity": "sha512-bY6fj56OUQ0hU1KjFNDQuJFezqKdrAyFdIevADiqrWHwSlbmBNMHp5ak2f40Pm8JTFyM2mqxkG6ngkHO11f/lg=="
+					"version": "5.0.1",
+					"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
+					"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ=="
 				}
 			}
 		},
@@ -24491,9 +24464,9 @@
 			}
 		},
 		"url-parse": {
-			"version": "1.5.1",
-			"resolved": "https://registry.npmjs.org/url-parse/-/url-parse-1.5.1.tgz",
-			"integrity": "sha512-HOfCOUJt7iSYzEx/UqgtwKRMC6EU91NFhsCHMv9oM03VJcVo2Qrp8T8kI9D7amFf1cu+/3CEhgb3rF9zL7k85Q==",
+			"version": "1.5.4",
+			"resolved": "https://registry.npmjs.org/url-parse/-/url-parse-1.5.4.tgz",
+			"integrity": "sha512-ITeAByWWoqutFClc/lRZnFplgXgEZr3WJ6XngMM/N9DMIm4K8zXPCZ1Jdu0rERwO84w1WC5wkle2ubwTA4NTBg==",
 			"requires": {
 				"querystringify": "^2.1.1",
 				"requires-port": "^1.0.0"
@@ -24732,11 +24705,11 @@
 			}
 		},
 		"webpack-dev-server": {
-			"version": "3.11.2",
-			"resolved": "https://registry.npmjs.org/webpack-dev-server/-/webpack-dev-server-3.11.2.tgz",
-			"integrity": "sha512-A80BkuHRQfCiNtGBS1EMf2ChTUs0x+B3wGDFmOeT4rmJOHhHTCH2naNxIHhmkr0/UillP4U3yeIyv1pNp+QDLQ==",
+			"version": "3.11.3",
+			"resolved": "https://registry.npmjs.org/webpack-dev-server/-/webpack-dev-server-3.11.3.tgz",
+			"integrity": "sha512-3x31rjbEQWKMNzacUZRE6wXvUFuGpH7vr0lIEbYpMAG9BOxi0928QU1BBswOAP3kg3H1O4hiS+sq4YyAn6ANnA==",
 			"requires": {
-				"ansi-html": "0.0.7",
+				"ansi-html-community": "0.0.8",
 				"bonjour": "^3.5.0",
 				"chokidar": "^2.1.8",
 				"compression": "^1.7.4",

website/versioned_docs/version-2.0.0/user-guides/gitops-configuration.md

@@ -17,8 +17,6 @@ GitOps enables you to configure a single source of truth for your chaos workflow
 
 ## Steps to configure GitOps
 
-
-
 - Setup a git repository, so that the ChaosCenter can sync with it, and push all the workflows in that repository.
 - The git repo can be public or private but for authorization, you have to provide an access token or any other mode of authentication.
 - Login into ChaosCenter, go to `GitOps` tab under `Settings`.
@@ -37,8 +35,11 @@ GitOps enables you to configure a single source of truth for your chaos workflow
 - Some metadata will be pushed to your repository, that is the projectID of your project.
 - Now whenever you schedule a workflow, it will automatically be pushed to your repository. And that repository will be the single source of truth.
 
-## Steps to configure Event-Triggered Chaos Injection
+:::note
+It is also possible to account for the workflows that are created and pushed to the git repository directly, after configuring GitOps. In this case, if the workflow is a single run workflow, then it starts executing as soon as it is pushed to the repository. Alternatively, if the workflow is a scheduled workflow, then it executes as per the defined schedule. On the other hand, updating an existing workflow present in the git repository will not execute the workflow but only sync the workflow resource definition with the ChaosCenter, if applicable.
+:::
 
+## Steps to configure Event-Triggered Chaos Injection
 
 - Once the workflow is pushed to your repository, you’ll notice every workflow has a `workflow_id`. You can get this from the workflow YAML file. You need to copy the id and annotate the target application so that if there’s any change in the application, gitops will sync the workflow using this workflow_id and run it on your target application. You can use the following command:
 

website/versioned_docs/version-2.1.0/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/versioned_docs/version-2.1.0/user-guides/gitops-configuration.md

@@ -17,8 +17,6 @@ GitOps enables you to configure a single source of truth for your chaos workflow
 
 ## Steps to configure GitOps
 
-
-
 - Setup a git repository, so that the ChaosCenter can sync with it, and push all the workflows in that repository.
 - The git repo can be public or private but for authorization, you have to provide an access token or any other mode of authentication.
 - Login into ChaosCenter, go to `GitOps` tab under `Settings`.
@@ -37,8 +35,11 @@ GitOps enables you to configure a single source of truth for your chaos workflow
 - Some metadata will be pushed to your repository, that is the projectID of your project.
 - Now whenever you schedule a workflow, it will automatically be pushed to your repository. And that repository will be the single source of truth.
 
-## Steps to configure Event-Triggered Chaos Injection
+:::note
+It is also possible to account for the workflows that are created and pushed to the git repository directly, after configuring GitOps. In this case, if the workflow is a single run workflow, then it starts executing as soon as it is pushed to the repository. Alternatively, if the workflow is a scheduled workflow, then it executes as per the defined schedule. On the other hand, updating an existing workflow present in the git repository will not execute the workflow but only sync the workflow resource definition with the ChaosCenter, if applicable.
+:::
 
+## Steps to configure Event-Triggered Chaos Injection
 
 - Once the workflow is pushed to your repository, you’ll notice every workflow has a `workflow_id`. You can get this from the workflow YAML file. You need to copy the id and annotate the target application so that if there’s any change in the application, gitops will sync the workflow using this workflow_id and run it on your target application. You can use the following command:
 

website/versioned_docs/version-2.2.0/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/versioned_docs/version-2.2.0/user-guides/gitops-configuration.md

@@ -17,8 +17,6 @@ GitOps enables you to configure a single source of truth for your chaos workflow
 
 ## Steps to configure GitOps
 
-
-
 - Setup a git repository, so that the ChaosCenter can sync with it, and push all the workflows in that repository.
 - The git repo can be public or private but for authorization, you have to provide an access token or any other mode of authentication.
 - Login into ChaosCenter, go to `GitOps` tab under `Settings`.
@@ -37,8 +35,11 @@ GitOps enables you to configure a single source of truth for your chaos workflow
 - Some metadata will be pushed to your repository, that is the projectID of your project.
 - Now whenever you schedule a workflow, it will automatically be pushed to your repository. And that repository will be the single source of truth.
 
-## Steps to configure Event-Triggered Chaos Injection
+:::note
+It is also possible to account for the workflows that are created and pushed to the git repository directly, after configuring GitOps. In this case, if the workflow is a single run workflow, then it starts executing as soon as it is pushed to the repository. Alternatively, if the workflow is a scheduled workflow, then it executes as per the defined schedule. On the other hand, updating an existing workflow present in the git repository will not execute the workflow but only sync the workflow resource definition with the ChaosCenter, if applicable.
+:::
 
+## Steps to configure Event-Triggered Chaos Injection
 
 - Once the workflow is pushed to your repository, you’ll notice every workflow has a `workflow_id`. You can get this from the workflow YAML file. You need to copy the id and annotate the target application so that if there’s any change in the application, gitops will sync the workflow using this workflow_id and run it on your target application. You can use the following command:
 

website/versioned_docs/version-2.2.0/user-guides/upgrade.md

@@ -37,4 +37,4 @@ Alternatively you can run the following command using litmusctl in the cluster c
 litmusctl upgrade agent --cluster-id="<CLUSTER_ID>" --project-id="<PROJECT_ID>"
 ```
 
-> Note: v0.5.0 of [litmusctl](https://github.com/litmuschaos/litmusctl/blob/master/README.md) is required.
+> Note: v0.5.0 of [litmusctl](https://github.com/litmuschaos/litmusctl/blob/master/README.md) is required.

website/versioned_docs/version-2.3.0/user-guides/gitops-configuration.md

@@ -37,8 +37,11 @@ GitOps enables you to configure a single source of truth for your chaos workflow
 - Some metadata will be pushed to your repository, that is the projectID of your project.
 - Now whenever you schedule a workflow, it will automatically be pushed to your repository. And that repository will be the single source of truth.
 
-## Steps to configure Event-Triggered Chaos Injection
+:::note
+It is also possible to account for the workflows that are created and pushed to the git repository directly, after configuring GitOps. In this case, if the workflow is a single run workflow, then it starts executing as soon as it is pushed to the repository. Alternatively, if the workflow is a scheduled workflow, then it executes as per the defined schedule. On the other hand, updating an existing workflow present in the git repository will not execute the workflow but only sync the workflow resource definition with the ChaosCenter, if applicable.
+:::
 
+## Steps to configure Event-Triggered Chaos Injection
 
 - Once the workflow is pushed to your repository, you’ll notice every workflow has a `workflow_id`. You can get this from the workflow YAML file. You need to copy the id and annotate the target application so that if there’s any change in the application, gitops will sync the workflow using this workflow_id and run it on your target application. You can use the following command:
 

website/versioned_docs/version-2.4.0/user-guides/gitops-configuration.md

@@ -37,8 +37,11 @@ GitOps enables you to configure a single source of truth for your chaos workflow
 - Some metadata will be pushed to your repository, that is the projectID of your project.
 - Now whenever you schedule a workflow, it will automatically be pushed to your repository. And that repository will be the single source of truth.
 
-## Steps to configure Event-Triggered Chaos Injection
+:::note
+It is also possible to account for the workflows that are created and pushed to the git repository directly, after configuring GitOps. In this case, if the workflow is a single run workflow, then it starts executing as soon as it is pushed to the repository. Alternatively, if the workflow is a scheduled workflow, then it executes as per the defined schedule. On the other hand, updating an existing workflow present in the git repository will not execute the workflow but only sync the workflow resource definition with the ChaosCenter, if applicable.
+:::
 
+## Steps to configure Event-Triggered Chaos Injection
 
 - Once the workflow is pushed to your repository, you’ll notice every workflow has a `workflow_id`. You can get this from the workflow YAML file. You need to copy the id and annotate the target application so that if there’s any change in the application, gitops will sync the workflow using this workflow_id and run it on your target application. You can use the following command: