You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using licensed prisma cloud twistlock defender daemon set to scan the pods around Azure kubernetes cluster.
Is it possible to exclude the pods in kube-system namespace. Thepods in it are not in our control and public cloud provider doesn't act immediately on the basis of reports of twistlock scanner. Hence, it is raising the alarms which can't be resolved by us or not in our control.
Is it possible to bypass it via helm chart values or something else.. Please suggest
The text was updated successfully, but these errors were encountered:
We are using licensed prisma cloud twistlock defender daemon set to scan the pods around Azure kubernetes cluster.
Is it possible to exclude the pods in kube-system namespace. Thepods in it are not in our control and public cloud provider doesn't act immediately on the basis of reports of twistlock scanner. Hence, it is raising the alarms which can't be resolved by us or not in our control.
Is it possible to bypass it via helm chart values or something else.. Please suggest
The text was updated successfully, but these errors were encountered: