From the course: Kubernetes and Cloud Native Security Associate (KCSA) Cert Prep

Unlock the full course today

Join today to access over 24,700 courses taught by industry experts.

Isolation techniques

Isolation techniques

All right. So what we're going to do here is we're going to do a quick overview of Kubernetes isolation. And you might hear me say this a few other times in this section. But as we dive into the other sections, we're going to be essentially taking everything that we've learned from this section, Section 1, and diving into it further. So we're going to be talking about namespaces, network policies, policy enforcement, and RBAC. So when it comes to isolation from a Kubernetes perspective, there are three main factors. Well, sorry four; namespaces, network policies, RBAC, and policy enforcement. I don't want to go too far down the rabbit hole right now, but let's do it at a high level. Now, namespaces give you the ability to logically isolate. So for example, App A and Namespace A and App B and Namespace B. However, they don't provide true security as apps can still talk to each other in various namespaces. But what they do do is give the ability to do things like set up network policies…

Contents