Bulat

I haven't thought about patches, thank you, will try it

Wrote this workaround ```yaml apiVersion: piraeus.io/v1 kind: LinstorSatelliteConfiguration metadata: name: register-infiniband spec: podTemplate: spec: containers: - name: register-indiniband command: - bash - -c - | echo "Checking that node exists...

I think it should be fixed here https://github.com/secureCodeBox/secureCodeBox/blob/main/auto-discovery/kubernetes/controllers/container_scan_controller.go#L422 Maybe we can ignore NotFound error

Oh, I see `getOrphanedScanImageIDs` in case of error just returns empty array, so this must not affect other events

Btw if I deploy container to the same namespace as auto-discovery service it won't work. Just no action when creating container

I definitely annotated namespace, because service log warning about non-existent scan type during direst deployment. After that I created scan type. Also service sees when pod is deleted and logs...

But serviceDiscovery works in the same namespace, containerDiscovery - no. There are just no logs.

As workaround you can pass `INHERITED_LABELS` to configmap/secret of the operator my `values.yaml` ```yaml config: data: INHERITED_LABELS: finops ``` Definition from the [doc](https://cloudnative-pg.io/documentation/1.20/operator_conf/) > list of label names that, when...

It's not stale, mentioned issues are waiting for approval

I think we can close the issue, so if you want teleport in kubernetes, the best way to deploy it as LoadBalancer, not behind the Istio/Nginx.