Using Argo CD and Rancher for Kubernetes Multi-tenancy & GitOps

Kubernetes multi-tenancy is one of the biggest challenges when operating Kubernetes at scale. It's not easy figuring out the best way to manage, organize and isolate teams and unrelated workloads on shared clusters. In some cases, you might have one big cluster, and in other cases, you might have multiple big clusters housing different teams and workloads. In this video, I talk about how organization and isolation are the foundation for the more popular best practices like namespaces, resource management, network policies, and RBAC. I also demonstrate how to make use of Rancher and Argo CD for Kubernetes multi-tenancy use cases.
#kubernetes #gitops #rancher
Rancher: rancher.com/
Argo CD: argo-cd.readthedocs.io/en/stable/
Timestamps:
00:00 - Introduction
00:06 - Overview
00:30 - Best practices
00:43 - Organization and isolation in Kubernetes clusters
00:50 - Rancher and Argo CD
01:00 - Projects in Rancher and Argo CD
01:15 - Projects in Rancher
02:15 - Projects in Argo CD
03:16 - AuthN, RBAC, projects and resource management in Rancher
12:57 - AuthN, RBAC and projects in Argo CD
Connect:
GitHub: github.com/LukeMwila
Twitter: LuKE9ine
Medium: medium.com/@outlier.developer
LinkedIn: www.linkedin.com/in/lukonde-mwila-25103345/
If you found this video helpful, please like the video and subscribe to the channel!

[@michaelcrenshaw6405]

Excellent video as always! One additional recommendation I'll offer: have a project dedicated solely to the parent app-of-apps. The ability to deploy resources to the argocd namespace is an admin-level capability and is worth siloing as much as possible.

[@LukondeMwila]

Great recommendation Michael! Really appreciate that tip.

[@georgevazj]

Great! Thanks for your work!

[@ebenezermakinde8352]

Great video .

[@TechyWithLorna]

Thank you for the video, so helpful

[@uziboozy4540]

I'd love to see an environment per tenant architecture using vcluster and Gitlab CI/CD or Octopus Deploy.