Can we incorporate database schema migrations into our processes? Can we do it in a Kubernetes-native way and through GitOps tools like Argo CD or Flux? Can SchemaHero be Managing multiple Kubernetes clusters can easily become a burdan. Giving each tenant a Namespace might be too limiting. Can we combine both? Can we solve the multi-tenancy problem by using virtual Kubernetes clusters? Can vcluster from loft be the solution?

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬

➡ Gist with the commands: https://gist.github.com/2dbb2f8683e661eaf0446f10b6974efb
🔗 vcluster: https://www.vcluster.com
🎬 Capsule: https://youtu.be/H8bzEJN7fj8

▬▬▬▬▬▬ 🚀 Courses, books, and podcasts 🚀 ▬▬▬▬▬▬

📚 DevOps Catalog, Patterns, And Blueprints: https://www.devopstoolkitseries.com/posts/catalog/
📚 Books and courses: https://www.devopstoolkitseries.com
🎤 Podcast: https://www.devopsparadox.com/
💬 Live streams: https://www.youtube.com/c/DevOpsParadox

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

➡ Follow me on Twitter: https://twitter.com/vfarcic
➡ Follow me on LinkedIn: https://www.linkedin.com/in/viktorfarcic/