diff --git a/README.md b/README.md
index 2c53d96..d594e85 100644
--- a/README.md
+++ b/README.md
@@ -101,3 +101,420 @@ helm upgrade --install armo  armo/armo-cluster-components -n armo-system --creat
 | volumeMounts | object | `[]` | Additional volumeMounts for all containers |
 
 
+# In-cluster components overview
+
+An overview of each in-cluster component which is part of the Kubescpae platform helm chart.
+Follow the repository link for in-depth information on a specific component.
+
+---
+
+## High-level Architecture Diagram
+
+```mermaid
+graph TB
+
+  client([client]) .-> dashboard
+  masterGw  .- gw
+
+  subgraph Cluster
+    gw(Gateway)
+    kontroller(Kontroller)
+    k8sApi(Kubernetes API);
+    kubevuln(Kubevuln)
+    ks(Kubescape)
+    gw --- kontroller
+    kontroller -->|scan cluster| ks
+    kontroller -->|scan images| kubevuln
+    kontroller --> k8sApi
+    ks --> k8sApi
+  end;
+  
+subgraph Backend
+    er(EventReceiver)
+    dashboard(Dashboard) --> masterGw("Master Gateway") 
+    ks --> er
+    kubevuln --> er
+  end;
+  
+  classDef k8s fill:#326ce5,stroke:#fff,stroke-width:1px,color:#fff;
+  classDef plain fill:#ddd,stroke:#fff,stroke-width:1px,color:#000;
+  class k8sApi k8s
+  class ks,kontroller,gw,masterGw,kollector,kubevuln,er,dashboard plain
+```
+
+---
+
+## [Gateway](https://github.com/kubescape/gateway)
+
+* __Resource Kind:__ `Deployment`
+* __Communication:__ REST API, Websocket
+* __Responsibility:__ Broadcasts a message received to its registered clients. When a client registers itself in a Gateway it must provide a set of attributes, which will serve as identification, for message routing purposes.
+
+  In our architecture, the Gateway acts both as a server and a client, depending on its running configuration:
+  * Master Gateway: Refers to the instance running in the backend. Broadcasts messages to all of its registered Gateways.
+  * In-cluster Gateway: Refers to the instance running in the cluster. Registered to the Master Gateway using a websocket; Broadcasts messages to the different in-cluster components, this enables executing actions in runtime.
+
+  A Master Gateway communicates with multiple in-cluster Gateways, hence it is able to communicate with multiple clusters.
+
+<details><summary>Component Diagram</summary>
+
+```mermaid
+graph TB
+  subgraph Backend
+   dashboard(Dashboard)
+    masterGw("Gateway (Master)") 
+  end
+   subgraph Cluster N
+    gw3("Gateway (In-cluster)")
+    kontroller3(Kontroller)
+  end;
+  subgraph Cluster 2
+    gw2("Gateway (In-cluster)")
+    kontroller2(Kontroller)
+  end;
+   
+subgraph Cluster 1
+    gw1("Gateway (In-cluster)")
+    kontroller1(Kontroller)
+  end;
+  dashboard --> masterGw
+   masterGw .- gw2
+   masterGw .- gw3
+       gw1 .- kontroller1
+    gw2 .- kontroller2
+    gw3 .- kontroller3
+   masterGw .- gw1
+
+    
+  classDef k8s fill:#326ce5,stroke:#fff,stroke-width:1px,color:#fff;
+  classDef plain fill:#ddd,stroke:#fff,stroke-width:1px,color:#000;
+  class k8sApi k8s
+  class ks,kontroller1,dashboard,kontroller2,kontroller3 plain
+```
+
+</details>
+
+---
+
+## [Kontroller](https://github.com/kubescape/kontroller)
+
+* __Resource Kind:__ `Deployment`
+* __Communication:__ REST API, Websocket
+* __Responsibility:__ The Kontroller component is at the heart of the solution as it is the triggering engine for the different actions in the cluster, It responds to REST API requests and messages received over websocket connection, and triggers the relevant action in the cluster. Such actions could be triggering a configuration scan, image vulnerability scan, defining a recurring scan (by creating CronJobs), etc.
+
+<details><summary>Component Diagram</summary>
+
+```mermaid
+graph TB
+  subgraph Cluster
+    gw(Gateway)
+    kontroller(Kontroller)
+    k8sApi(Kubernetes API);
+    kubevuln(Kubevuln)
+    ks(Kubescape)
+    urlCm{{ConfigMap<br>URLs}}
+    recurringTempCm{{ConfigMap<br>Recur. Scan Template}}
+    recurringScanCj{{CronJob<br>Recurring Scan}}
+  end;
+   masterGw(Master Gateway) .- gw
+    gw ---> kontroller
+    recurringScanCj ---> kontroller
+    recurringScanCj --> recurringScanCj
+    kontroller -->|scan cluster| ks
+    kontroller -->|scan images| kubevuln
+    kontroller --> k8sApi
+    kontroller --- urlCm
+    kontroller --- recurringTempCm
+  
+  classDef k8s fill:#326ce5,stroke:#fff,stroke-width:1px,color:#fff;
+  classDef plain fill:#ddd,stroke:#fff,stroke-width:1px,color:#000;
+  class k8sApi k8s
+  class ks,gw,masterGw,kollector,urlCm,recurringScanCj,recurringTempCm,kubevuln,er,dashboard plain
+```
+
+</details>
+
+---
+
+## [Kubevuln](https://github.com/kubescape/kubevuln/)
+
+* __Resource Kind:__ `Deployment`
+* __Communication:__ REST API
+* __Responsibility:__ Scans container images for vulnerabilities, using [Grype](https://github.com/anchore/grype) as its engine.
+
+<details><summary>Component Diagram</summary>
+
+```mermaid
+graph TB
+
+subgraph Cluster
+    kubevuln(Kubevuln)  
+    k8sApi(Kubernetes API)
+    kontroller(Kontroller)
+    gateway(Gateway)
+    urlCm{{ConfigMap<br>URLs}}
+    recurringScanCj{{CronJob<br>Recurring Scan}}
+    recurringScanCm{{ConfigMap<br>Recurring Scan}}
+    recurringTempCm{{ConfigMap<br>Recurring Scan Template}}
+
+end
+
+masterGateway  .- gateway
+gateway .-|Scan Notification| kontroller 
+kontroller -->|Collect NS, Images|k8sApi
+kontroller -->|Start Scan| kubevuln
+kontroller --- urlCm
+urlCm --- kubevuln 
+recurringTempCm --- kontroller
+recurringScanCj -->|Periodic Run| recurringScanCj
+recurringScanCj -->|Scan Notification| kontroller
+recurringScanCm --- recurringScanCj
+
+subgraph Backend
+    er(EventReceiver)
+    masterGateway("Master Gateway") 
+    kubevuln -->|Scan Results| er
+end;
+
+classDef k8s fill:#326ce5,stroke:#fff,stroke-width:1px,color:#fff;
+classDef plain fill:#ddd,stroke:#fff,stroke-width:1px,color:#000
+
+class k8sApi k8s
+class urlCm,recurringScanCm,kontroller,er,gateway,masterGateway,recurringScanCj,recurringTempCm plain
+
+
+```
+</details>
+
+---
+
+## [Kubescape](https://github.com/armosec/kubescape/tree/master/httphandler)
+
+* __Resource Kind:__ `Deployment`
+* __Communication:__ REST API
+* __Responsibility:__ Runs [Kubescape](https://github.com/armosec/kubescape) for detecting misconfigurations in the cluster, This microservice uses the same engine as the Kubescape CLI tool.
+
+<details><summary>Component Diagram</summary>
+
+```mermaid
+graph TB
+
+subgraph Cluster
+    ks(Kubescape)  
+    k8sApi(Kubernetes API)
+    kontroller(Kontroller)
+    gateway(Gateway)
+    ksCm{{ConfigMap<br>Kubescape}}
+    recurringScanCj{{CronJob<br>Recurring Scan}}
+    recurringScanCm{{ConfigMap<br>Recurring Scan}}
+    recurringTempCm{{ConfigMap<br>Recurring Scan Template}}
+end
+
+masterGateway  .- gateway
+gateway .-|Scan Notification| kontroller 
+kontroller -->|Start Scan| ks
+ks-->|Collect Cluster Info|k8sApi
+ksCm --- ks 
+recurringTempCm --- kontroller
+recurringScanCj -->|Periodic Run| recurringScanCj
+recurringScanCj -->|Scan Notification| kontroller
+recurringScanCm --- recurringScanCj
+subgraph Backend
+    er(EventReceiver)
+    masterGateway("Master Gateway") 
+    ks -->|Scan Results| er
+end;
+
+classDef k8s fill:#326ce5,stroke:#fff,stroke-width:1px,color:#fff;
+classDef plain fill:#ddd,stroke:#fff,stroke-width:1px,color:#000
+
+class k8sApi k8s
+class ksCm,recurringScanCm,kontroller,er,gateway,masterGateway,recurringScanCj,recurringTempCm plain
+
+
+```
+
+</details>
+
+---
+
+## [Kollector](https://github.com/kubescape/kollector)
+
+* __Resource Kind:__ `StatefulSet`
+* __Responsibility:__ Communicates with the Kubernetes API server to collect cluster information and watches for changes in the cluster. Information is reported to the backend via the EventReceiver and the Gateway.
+
+<details><summary>Component Diagram</summary>
+
+```mermaid
+graph TD
+subgraph Backend
+    er(EventReceiver)
+    masterGw("Master Gateway") 
+end;
+
+subgraph Cluster
+    kollector(Kollector) 
+    k8sApi(Kubernetes API);
+    gw(Gateway)
+end;
+
+kollector .->|Scan new image| gw
+masterGw  .- gw
+kollector --> er
+kollector --> k8sApi
+
+classDef k8s fill:#326ce5,stroke:#fff,stroke-width:1px,color:#fff;
+classDef plain fill:#ddd,stroke:#fff,stroke-width:1px,color:#000;
+class k8sApi k8s
+class er,gw,masterGw plain
+```
+
+</details>
+
+---
+
+## [URLs ConfigMap](https://github.com/armosec/armo-helm/blob/master/charts/armo-components/templates/armo-configmap.yaml)
+
+Holds a list of communication URLs. Used by the following components:
+
+* Kontroller
+* Kubevuln
+* Gateway
+
+<details><summary>Config Example (YAML)</summary>
+
+```yaml
+gatewayWebsocketURL: 127.0.0.1:8001                             # component: in-cluster gateway
+gatewayRestURL: 127.0.0.1:8002                                  # component: in-cluster gateway
+kubevulnURL: 127.0.0.1:8081                                     # component: kubevuln
+kubescapeURL: 127.0.0.1:8080                                    # component: kubescape
+eventReceiverRestURL: https://report.cloud.com                  # component: eventreceiver
+eventReceiverWebsocketURL: wss://report.cloud.com               # component: eventreceiver
+rootGatewayURL: wss://masterns.cloud.com/v1/waitfornotification # component: master gateway
+accountID: 1111-aaaaa-4444-555
+clusterName: minikube
+```
+</details>
+
+---
+
+## Kubernetes API
+
+Some in-cluster components communicate with the Kubernetes API server for different purposes:
+
+* Kollector
+
+  Watches for changes in namespace, workloads, nodes. Reports information to the EventReceiver. Identifies image-related changes and triggers an image scanning on the new images accordingly (scanning new images functionality is optional).
+
+* Kontroller
+
+  Creates/updates/deletes resources for recurring scan purposes (CronJobs, ConfigMaps). Collects required information (NS, image names/tags) for Kubevuln's image scanning.
+
+* Kubescape
+
+  Collects namespaces, workloads, RBAC etc. required for cluster scans.
+
+---
+
+## Backend components
+
+The backend components are running in [Kubescape's SaaS offering](https://cloud.armosec.io/).
+
+### Dashboard
+
+* REST API service
+
+### EventReceiver
+
+* __Responsibility:__ Receive and process Kubescape & Kubevuln scan results.
+* __Communication:__ REST API
+
+---
+
+## Logging and troubleshooting
+
+Each component writes logs to the standard output.
+
+Every action has a generated `jobId` which is written to the log.
+
+An action which creates sub-action(s), will be created with a different `jobId` but with a `parentId` which will correlate to the parent action's `jobId`.
+
+---
+
+## Recurring scans
+
+3 types of recurring scans are supported:
+
+  1. Cluster configuration scanning (Kubescape)
+  2. Vulnerability scanning for container images (Kubevuln)
+  3. Container registry scanning (Kubevuln)
+
+When creating a recurring scan, the Kontroller component will create a `ConfigMap` and a `CronJob` from a recurring template ConfigMap. Each scan type comes with a template.
+
+The CronJob itself does not run the scan directly. When a CronJob is ready to run, it will send a REST API request to the Kontroller component, which will then trigger the relevant scan (similarly to a request coming from the Gateway).
+
+The scan results are then sent by each relevant component to the EventReceiver.
+
+### Main Flows Diagrams
+
+<details><summary>Recurring Scan Creation</summary>
+
+
+```mermaid
+sequenceDiagram
+    actor user
+    participant dashboard as Backend<br><br>Dashboard
+    participant masterGw as Backend<br><br>Master Gateway
+    participant clusterGw as Cluster<br><br>In-Cluster Gateway
+    participant kontroller as Cluster<br><br>Kontroller
+    participant k8sApi as Cluster<br><br>Kubernetes API
+    
+    user->>dashboard: 1. create scan schedule
+    dashboard->>masterGw: 2. build schedule notification
+    masterGw->>clusterGw: 3. broadcast notification
+    clusterGw->>kontroller: 4. create recurring scan
+    kontroller->>k8sApi: 5. get namespaces, workloads
+    k8sApi-->>kontroller: 
+    kontroller->>k8sApi: 6. Create cronjob & ConfigMap
+```
+</details>
+
+<details><summary>Recurring Image Scan</summary>
+
+```mermaid
+sequenceDiagram
+   participant cronJob as Cluster<br><br>CronJob
+   participant kontroller as Cluster<br><br>Kontroller
+   participant k8sApi as Cluster<br><br>Kubernetes API
+   participant kubeVuln as Cluster<br><br>Kubevuln
+   participant er as Backend<br><br>EventReceiver
+   loop
+      cronJob->>kontroller: 1. run image scan
+   end
+   kontroller->>k8sApi: 2. list NS, container images
+   k8sApi-->>kontroller: 
+   kontroller->>kubeVuln: 3. scan images
+   kubeVuln ->> er: 4. send scan results
+```
+
+</details>
+
+<details><summary>Recurring Kubescape Scan</summary>
+
+```mermaid
+sequenceDiagram
+  participant cronJob as Cluster<br><br>CronJob
+  participant kontroller as Cluster<br><br>Kontroller
+  participant ks as Cluster<br><br>Kubescape
+  participant k8sApi as Cluster<br><br>Kubernetes API
+  participant er as Backend<br><br>EventReceiver
+  loop
+      cronJob->>kontroller: 1. run configuration scan
+  end
+  kontroller->>ks: 2. kubescape scan 
+  ks->>k8sApi: 3. list NS, workloads, RBAC 
+  k8sApi->>ks: 
+  ks ->> er: 4. send scan results
+```
+
+</details>