This message was deleted.
# neuvector-security
a
This message was deleted.
f
We also see in the events of the controllers that the readiness probe fails cat: can't open "/tmp/ready': No such file or directory. Then the controller is killed and a new one is started, but the new controller has the same problem
q
That does seem like a lot of ram, agreed. DO you have a lot of rules, or a lout of images with a lot of CVEs that are trying to phone in?
Controllers are not necessarily load-balanced; they are HA
f
Thanks for your response. We don’t have many rules set; we just started creating them. There are 1718 pods running on this cluster, and the current mode is set to discover.
If we look at the logs of the controllers, we see a lot of 404 fault codes. Sample log:
2024-04-09T06:33:19.036|ERRO|CTL|cache.updateK8sPodEvent: get ressource - domain=test error=kubernetes api: Failure 404 pods "workspace123" not found group=nv.workspace-group pod=workspace123
We are running v5.2.4