How can we create and manage Kubernetes clusters on-prem or in Cloud? How can we manage our clusters across providers and regions? Can Rancher and Rancher Kubernetes Engine (RKE) help us with those and other similar tasks? Can we use it to manage clusters no matter whether they are in AWS, Azure, Google Cloud (GCP), DigitalOcean, Linode, VMWare, and other Cloud providers as well as in our own on-prem datacenters?
What is a monorepo and why you should care? Why would you use mono-repo in the first place? What are the differences between mono repo and polyrepo or multirepo? What are the pros and cons of monorepo? Should you switch to monorepo or keep using poly-repos or multi-repos?
How do we version software? Should we use build numbers, Semantic Versioning (SemVer), Calendar Versions (CalVer), milestone versioning, or something else? What are the reasons for using each of those and which one should you use?
Tekton is a powerful and flexible open-source framework for creating CI/CD systems aiming at becoming a de-facto standard for running pipelines and workflows in Kubernetes. It allows developers to build, test, and deploy across cloud providers and on-premise systems.
What are different branching strategies? Which Git branching strategy should you be using? Should it be trunk-based development, feature branches, GitHub Flow, forking strategy, release branching, Git Flow, environment branches, or something completely different?
What is GitHub actions? How to use GitHub Actions, and does it work? How can we leverage its marketplace, and what is the pricing? Is it a good solution for CI/CD pipelines? Let’s answer those and other questions through tutorial and review.