Workload Isolation
Let's explore some techniques for isolating workloads.
This section will show us some ways we can use to isolate workloads.
We’ll start at the cluster level, switch to the runtime level, and then look outside the cluster at infrastructure such as network firewalls.
Cluster-level workload isolation
Cutting straight to the chase, Kubernetes does not support secure multi-tenant clusters. The only way to isolate two workloads is to run them on their own clusters with their own hardware.
Let’s look a bit closer.
The only way to divide a Kubernetes cluster is by creating Namespaces. However, these are little more than a way of grouping resources and applying things such as:
Limits
Quotas
RBAC rules
Namespaces do not prevent compromised workloads in one Namespace from impacting workloads in other Namespaces. This means we should never run hostile workloads on the same Kubernetes cluster. ...