Skip to content

Detector Deployment and Architecture

K8S Anomaly Detector Operator supports creating a CR which propagtes a few other Kubernetes resources:

  • Deployment
  • ConfigMap
  • ServiceAccount

The name of the Detector CR is propagated to the labels selectors and name of every resource it creates. 

...
kind: Detector
metadata:
  name: detector-name
...


> kubectl get cm,deploy,sa -n detectors

NAME                              DATA   AGE
configmap/detector-name           1      5m

NAME                              READY   AGE
deployment.apps/detector-name     1/1     5m

NAME                              SECRETS   AGE
serviceaccount/detector-name      0         5m

Deployment

The Deployment resource is desgined to run as a single replica pod.

Tip

If a Detector queries list is too long or the queries are too heavy it is reccomended to split it to smaller and distributed Detector resources

ConfigMap

The ConfigMap resource is created with the detector configurations from the Detector resource.

Note

If the spec of the Detector changes the ConfigMap will be updated with the new config and the Deployment will be rolled out in order to load the new ConfigMap.

ServiceAccount

The ServiceAccount resource is created by default and cannot be changed or modified. It is used as the Deployment serviceaccount and can be changed to a custom serviceaccount using the pod_spec on the Detector resource.