From ffcc1f11ce1748c09b6365dae2c782419a58d9c5 Mon Sep 17 00:00:00 2001
From: Amir Malka <amirm@armosec.io>
Date: Wed, 8 Jan 2025 12:43:39 +0200
Subject: [PATCH] deprecated microservices

Signed-off-by: Amir Malka <amirm@armosec.io>
---
 docs/docs/operator/index.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/docs/docs/operator/index.md b/docs/docs/operator/index.md
index 2209cde..80d9ae8 100644
--- a/docs/docs/operator/index.md
+++ b/docs/docs/operator/index.md
@@ -62,11 +62,16 @@ Several of our in-cluster components implement telemetry data using OpenTelemetr
 
 ## Automation and control
 
-* The `operator` and `gateway` microservices interact to start or [schedule](scheduled-scans.md) scans. 
-* The `kollector` service sends information about the state of the cluster to a configured [provider](../providers.md). 
+* The `operator` microservice handles the [scheduling](scheduled-scans.md) and execution of scans.
+* The `synchronizer` microservice sends information about the state of the cluster to a configured [provider](../providers.md). A connected provider can leverage the `synchronizer` to create OperatorCommand (CRDs), to instruct the `operator` to perform tasks such as executing scans or other supported actions of the operator.
 
 For information on how these services interact, [check out their documentation on GitHub.](https://github.com/kubescape/helm-charts/blob/main/charts/kubescape-operator/README.md)
 
+!!! Deprecated microservices
+
+    The kollector<sup>1</sup> and gateway<sup>2</sup> microservices were deprecated in Helm chart versions 1.24.0 and 1.25.0, respectively, and replaced by the synchronizer microservice.
+    > The `kollector`<sup>[1](https://github.com/kubescape/helm-charts/pull/559)</sup> and `gateway`<sup>[2](https://github.com/kubescape/helm-charts/pull/565)</sup> microservices have been deprecated and replaced by the `synchronizer` microservice in Helm chart versions 1.24.0 and 1.25.0, respectively.
+
 ## Node agent
 
 Some functions of Kubescape require access to every node.  These include controls which require [host scanning](../scanning.md#the-host-scanner), and [calculating runtime vulnerability relevancy](relevancy.md).