Skip to content

How to exclude namespace from scanning by twistlock daemon set? #649

Description

@smartaquarius10

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions