Kubernetes Network Policies are the feature that controls how Pods communicate with each other and external services. Option B is correct because Network Policies define rules for ingress (incoming) and egress (outgoing) traffic at the Pod level, ensuring fine-grained control over communication pathways within the cluster.
Option A (Pod Security Standards) defines policies around Pod security contexts (e.g., privilege escalation, root access) but does not control network traffic. Option C (Security Context) is specific to Pod or container-level permissions, not networking. Option D (RBAC) governs access to Kubernetes API resources, not Pod-to-Pod traffic.
Network Policies are essential for implementing a zero-trust model in Kubernetes, ensuring that only authorized services communicate. This enhances both security and compliance, especially in multi-tenant clusters.
[References:— CNCF Kubernetes Security Best Practices— CNCF Platforms Whitepaper— Cloud Native Platform Engineering Study Guide, , ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit