A municipal API gateway Pod is protected by a strict NetworkPolicy. Product still asks whether that alone authenticates callers. What should you tell them?
Select an answer to reveal the explanation.
Short Explanation
A NetworkPolicy is a street gate, not a photo ID check at the counter. It can stop packets from the wrong CIDR or Pod labels, but it does not log anyone in. Keep tokens, mTLS, or API keys in the app—or a proper auth layer—alongside the policy.
Full Explanation
Kubernetes NetworkPolicies enforce allow/deny rules on IP and port traffic (commonly described as L3/L4) based on selectors and ipBlocks. They do not authenticate callers, issue identity, or replace ServiceAccount tokens, mTLS, or application-level authn. Service selectors choose Endpoints; they are not credentials. Treat NetworkPolicy as traffic control complementary to authentication and authorization.