Is Kubernetes too complicated? Do you or the people working with you prefer ClickOps instead of terminals and writing manifests? Do you prefer SaaS solution running on your own infrastructure? If you do, Qovery might be a good fit for you. In this video, I will show you how to use Qovery to deploy an application with a managed database to Kubernetes.
How can we enable application developers to be self-sufficient instead of opening JIRA tickets requesting deployment of their apps to Kubernetes, creation of databases, clusters, etc.? In this video, I’m trying to answer that question through an example of a stateful application running in Kubernetes and connected to a database. To accomplish that, I’ll use Crossplane, SchemaHero, Okteto, and a bit of Bash scripting.
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.