Workload Isolation
Explore workload isolation techniques in Kubernetes to improve security. Learn about cluster-level namespaces, node isolation methods, runtime distinctions between containers and virtual machines, and network isolation strategies such as overlay and BGP networks. This lesson helps you understand how to secure and isolate workloads effectively within Kubernetes environments.
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 ...