GitOps practices and patterns
View All Tags
It started as an internal hackathon idea, we teased you about it in past livestreams, and it’s finally here: kubefirst now has a GitOps Catalog. Faithful to our goal to make Kubernetes adoption, and usage easier, this new catalog will make your life even better when it comes to adding new applications or tooling to your cluster while respecting the GitOps principles.
With this release, we are setting the foundation for the soon-to-be multi-clusters feature. By doing so, we introduced a more visual, and interactive way to create new management clusters. There are now more ways for you to create a management cluster, and have fun while doing so. It may not seem like much for a new release at first, but the engineering team was hard at work: they decoupled the logic from the CLI to create a shared library that also implements an API which will give us a consistent user experience. Read more to know how to jump the fun wagon, and swim in the new user experience.
Kubeshop sponsored this post.
It’s been a while since we released a new version of our CLI, but it's for a good reason: we were working hard on 2.0. We are really excited to share with you the new major release of the kubefirst platform, which includes a lot of new goodies! For those of you that are new with us, kubefirst delivers instant GitOps platforms so you can have the most popular open source platform tools working together in minutes.
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.
The Kubefirst 1.11 release continues the momentum our recent introduction of kubefirst local. The local environment is a fully automated local kubernetes cluster and gitops platform that includes some of the best open source tools like argo cd, vault, terraform automated with Atlantis, argo workflows, and so much more all working together.
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.
