Our great sponsors
-
gitflow
Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
The question of “How do I promote a release to the next environment?” is becoming increasingly popular among organizations that want to adopt GitOps. And even though there are several possible answers, in this particular article I want to focus on what you should NOT do.
And that is true. Most people are familiar with using branches for different environments. This practice was heavily popularized by the venerable Git-Flow model. But since the introduction of this model, things have changed a lot. Even the original author has placed a huge warning at the top advising people against adopting this model without understanding the repercussions.
Related posts
- Continue with LocalAI: An alternative to GitHub's Copilot that runs everything locally
- ArgoCD // Helm Chart // Dev/Staging // Your Best-Practise
- What is better Github or Devops? We of the kubernetes Dutch podcast interviewed April Edwards. Normally the podcast is in dutch but this episode is in englisch.
- win cool stuff with kubefirst's new video game flappy-kray (oh and we have a new ui too i guess)
- Argocd and Flux at the same time?