Skip to content
0:00 / 0:00

#kubernetesnamespaces#vcluster#multi-tenancy

Kubernetes Namespaces Offer No Isolation, and How You Can Work Around It

vCluster

2.8K subscribers • 1 video on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Made by the vendor. The company whose product it covers made or sponsored it.

Intermediate. Assumes working knowledge.

2K views2 years ago2 recommendations

Cloud and DevOpsSecurityKubernetesSoftware architectureWeb and application security

An in-depth look at how Kubernetes namespaces handle scheduling, networking, and RBAC, and how to achieve true multi-tenancy.

Kubernetes namespaces are the basic building block for identity and isolation but don't provide any of those features out of the box. In this session, you will explore in a great level of detail: - How namespaces are (not) used during scheduling. - How namespaces are (not) used in the cluster network and the implementation of Network Policies. - How namespaces provide the starting point for RBAC. The insights will help you understand the trade-offs in designing a multi-tenant platform on Kubernetes. ► Companion Blog: loft.sh/blog/kubernetes-namespaces-dont-exist ▬▬▬▬▬▬ Building a Multi-tenant Kubernetes Platform ▬▬▬▬▬▬ Part 1 Architecting Kubernetes Clusters: One Large Shared or Multiple Small Clusters ► youtu.be/LIITGz9QVvI Companion Blog ► loft.sh/blog/comparing-multi-tenancy-options-in-kubernetes/ Part 3 Building a Kubernetes Platform - Tools, and Techniques ► youtu.be/vy9ms3_FIVE Companion Blog ► loft.sh/blog/multi-tenancy-in-kubernetes-comparing-isolation… ►Where to follow and watch Loft: 👍 LinkedIn: linkedin.com/company/loft-sh 👍 Twitter: twitter.com/loft_sh 👍 YouTube: youtube.com/@loft_sh 👍 GitHub: github.com/loft-sh / @loft_sh 👍 Website: loft.sh/ #kubernetes #multitenancy #vcluster

Why it's here

2 people recommend this

What people say. Recommended for its detailed explanation of Kubernetes namespace isolation and multi-tenancy trade-offs.

u/mpetersen_loft-shin r/kubernetes • Recommends

Part 2 : Kubernetes Namespaces Offer No Isolation, and How You Can Work Around It (Plus some great info about how K8s works with scheduling/other)

u/Ok_Storm5443in r/sre • Recommends

On “Suggestion on Policies for Kyverno”

I am also looking at security in containers/K8s, and one of the things I have found, which poke my interest, is the following video: [video There are some ideas on namespaces and isolation that may be good to look into. There is also a companion blog to this video: https://www.vcluster.com/blog/kubernetes-namespaces-dont-exist Standard disclaimers apply. YMMV.