Chapter 13: Securing Kubernetes Clusters and Applications

1. Kubernetes itself does not provide a means for managing normal external users who access the cluster. This should be delegated to an external authentication provider that can integrate with Kubernetes, for example, via Authenticating Proxy.
2. To reduce the attack vector, the recommended practice is to never expose Kubernetes Dashboard using a LoadBalancer service and always use a kubectl proxy for accessing the page.
3. This will provide an extra layer of security for your API resources and Secrets, which otherwise would be kept in etcd in unencrypted form.

4. No, this feature is supported only in Linux containers.
5. NetworkPolicy objects define how groups of Pods can communicate with each other and network endpoints in general—think of them as a basic firewall for enforcing network segmentation at Layer 3 of the OSI...