Minimize access to secrets

Description:

The Kubernetes API stores secrets, which may be service account tokens for the Kubernetes API or credentials used by workloads in the cluster. Access to these secrets should be restricted to the smallest possible group of users to reduce the risk of privilege escalation.

Rationale:

Inappropriate access to secrets stored within the Kubernetes cluster can allow for an attacker to gain additional access to the Kubernetes cluster or external resources whose credentials are stored as secrets.

Care should be taken not to remove access to secrets to system components which require this for their operation

Where possible, remove 'get', 'list' and 'watch' access to 'secret' objects in the cluster.