Wouldn’t it be great if we would not need to define infrastructure but let applications themselves figure out what to do, where to run, and how to do all that? Klotho enables us to write Cloud-native microservices and applications and auto-magically get infrastructure and the code that ties it all together.
How much does it cost to run a Kubernetes cluster? How much do we spend on other Cloud resources? Can we break down the price per teams, services, namespaces, and other groups? Is Kubecost the answer to those questions? What is Kubecost?
Can we make Kubernetes disappear? Can we make infrastructure and application management so simple that anyone can do it? Can we leverage DevOps, SRE, ops, and sysadmin experience to create a system that would make developers autonomous? TL;DR We can do that by combining ArgoCD (GitOps), Crossplane (control plane), Kubevela (OAM), and a few other tools.
The 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.
AWS Fargate is the first fully managed Kubernetes service. Google Cloud Autopilot followed. Let’s compare EKS Fargate vs. GKE Autopilot and see what the differences are. Which one is better? Which one should we use? Continue reading →