A static content Pod never calls the Kubernetes API. Which setting reduces unnecessary credential exposure?
Select an answer to reveal the explanation.
Short Explanation
If the app never talks to the API, don't hang a VIP badge on it. Turn off automountServiceAccountToken so no token volume shows up by default. That shrinks the blast radius if the container is compromised.
Full Explanation
By default Kubernetes may automount a ServiceAccount token into Pods. For workloads that do not need API access, set automountServiceAccountToken to false on the Pod or ServiceAccount to avoid presenting unnecessary credentials. Granting cluster-admin, placing tokens in ConfigMaps, or enabling hostNetwork does not correctly minimize token exposure.