The security of the cluster mainly considers the following aspects:
- Isolation of the container from the host;
- Limiting the ability of containers to adversely affect infrastructure and other containers;
- The principle of least privilege--to reasonably restrict the permissions of all components, to ensure that the component only performs its mandated behavior, limiting the scope of the permissions it can achieve by restricting the ability of a single component;
- Defining the division of component boundaries;
- Dividing the roles of ordinary users and administrators;
- Allow administrator privileges to be assigned to ordinary users when necessary;
- Allows applications that have "Secret" data (keys,cert,passwords) to run in the cluster.
The Kubernetes cluster provides three levels of client identity authentication:
- The strictest HTTPS certificate authentication: Two-way Digital certificate authentication method based on CA root certificate signature;
- HTTPS token authentication: Identify legitimate users through a token;
- HTTP Base authentication: Authentication by user name + password;
kubernetes-in-depth analysis of cluster security mechanisms (3.6)