Rancher Desktop is Kubernetes and container management. As such, it could be a good replacement for Docker Desktop. Is that the case? Should we move from Docker Desktop to Rancher Desktop?
Continue readingHow do we develop microservices knowing that we cannot run the whole system locally? How do we connect local applications with microservices running in remote Kubernetes clusters? Can CodeZero be the solution?
Continue readingFly.io enable us to run apps across multiple regions without having to deal with operations. It is a global No-Ops solution.
Continue readingYou might have to pay to use Docker Desktop. It’s not “free for all” anymore. Fortunately, there are free alternatives, and we are going to choose the best one.
Continue readingTroubleshoot is a kubectl plugin providing diagnostic tools for Kubernetes clusters and applications. It provides means to troubleshoot potential issues as well as to generate a support bundle that can be sent to the team providing the support.
Continue readingKoncrete is cloud-hosted GitOps and continuous delivery (CD) service for Kubernetes built on top of Argo CD. It is effectively, ArgoCD-as-a-Service or GitOps-as-a-Service type of solution.
Continue readingWhy do we need chaos engineering? How does it work? What are the steps and the principles behind chaos engineering?
Continue readingApplication lifecycle typically consists of three parts. First, we develop locally, we deploy to temporary environments, usually due to creating pull requests, and we proceed towards a permanent environment, all the way until production. Can we streamline and simplify the whole application lifecycle process by combining Kubernetes, vCluster, DevSpace, Argo CD, k3d, and GitHub Actions? Even if you prefer a different combination, the principles behind this process can be easily applied to a myriad of other tools.
Continue readingKubeSphere Kubernetes platform is a distributed operating system for cloud-native application management. Should you use it?
Continue readingThe job of ops should not be to create and manage infrastructure for other teams. Instead, it should be to enable other teams to manage their own infra. It should be about creating tools and platforms that are opinionated, yet provide sufficient freedom for the teams, no matter whether they are using AWS, Azure, Google Cloud (GCP), or any other provider.
Continue reading
Technology Conversations 