docs: add Argo Rollouts plugin system architecture

Signed-off-by: Philipp Plotnikov <[email protected]>
argoproj-labs · Apr 25, 2024 · ff35f6f · ff35f6f
1 parent 090809c
commit ff35f6f
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 0 deletions.
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
@@ -26,6 +26,11 @@ cd rollouts-plugin-trafficrouter-gatewayapi
 
 ## Argo Rollouts plugin system architecture
 
+When Argo rollouts controller starts it requests the ConfigMap **argo-rollouts-config** from api server of k8s cluster and if it gets it, it validates its content before putting this ConfigMap in RAM. It is important to understand it happens only at the beginning and only one time, so if you will change **argo-rollouts-config** or you will add it after Argo Rollouts controller you will need to restart Argo Rollouts. Controller uses this config map to understand where specified in argo manifest plugins are. When Argo Rollouts learns their locations it downloads and executes them as seperate RPC servers in the same pod. When controller gets specific events, for example events corresponding to the SetWeight action, it makes specific remote procedure call to the needing RPC server and waits its response. Diagram illustrating the main aspects of architecture is below.
+
+![Argo rollouts plugin system architecture](./images/contributing/argo-rollouts-plugin-system-architecture.png)
+
+
 ## Project dependecies
 
 `go.mod` is used, so the `go build/test` commands automatically install the needed dependencies

diff --git a/docs/images/contributing/argo-rollouts-plugin-system-architecture.png b/docs/images/contributing/argo-rollouts-plugin-system-architecture.png