Of the many building blocks that go into deploying successfully to a Kubernetes cluster, it’s hard to get more essential than Argo CD. When you use it as part of your deployment workflow, it becomes the “puppetmaster” for getting all your applications and clusters into your desired state.
We love HashiCorp’s Terraform, but have one big reservation with how it gets used in ways that don’t respect proper GitOps practices. Most notably, the requirement that your system-level changes are handled in code and peer reviewed, with fully-auditable results.
Secret-scattering.
This phrase might conjure up an image of childhood games or harmless pranks, but for the Kubefirst team, it’s how we describe a practice that hamstrings even the most well-meaning engineering teams.
When folks try out Kubefirst and join our community for the first time, they tend to fall into two categories. First, there are those inside of established organizations, which are balancing their older technology with their ambition to adopt the cloud native landscape. Second, we have technical co-founders and early engineers at youthful startups, who just need to make that leap from “my application runs on localhost” to having development/staging/production Kubernetes environments.
Adopting Kubernetes and cloud native can be difficult and time consuming. Kubefirst's mission is to change this by producing cloud native platforms that are preconfigured, operational, and fully-automated from a single command. Throughout our project's history, we've focused our efforts on Kubernetes environments in public clouds. With our kubefirst cluster create command, your empty cloud will transform into a self-hosted open-source cloud native ecosystem running workloads in production in minutes instead of the months it would take to build from scratch.