Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deprecated microservices #84

Merged
merged 1 commit into from
Jan 13, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/docs/operator/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,11 +62,15 @@ 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)

!!! info "Deprecated microservices"

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 in Helm chart versions 1.24.0 and 1.25.0, respectively, and replaced by the `synchronizer` microservice.

## 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).
Expand Down