K8s-MultiTenancy

1. Supplementary Aspects Over Generic Multitenancy

1.1. Control and Data

  • Control Plane (masters)
  • Data Plane Tenancy

1.2. Kubelet & APIServer

Although workloads from different tenants are running on different nodes, it is important to be aware that the kubelet and (unless using virtual control planes) the API service are still shared services. A skilled attacker could use the permissions assigned to the kubelet or other pods running on the node to move laterally within the cluster and gain access to tenant workloads running on other nodes. If this is a major concern, consider implementing compensating controls such as seccomp, AppArmor or SELinux or explore using sandboxed containers or creating separate clusters for each tenant.

1.4. K8S DNS

Tags::cs:k8s: