# GitOps - [Introduction](#introduction) - [GitOps Working Group](#gitops-working-group) - [Git Repositories Structures](#git-repositories-structures) - [GitOps Tools](#gitops-tools) - [Flux. The GitOps Operator for Kubernetes](#flux-the-gitops-operator-for-kubernetes) - [Kustomize. Kubernetes native configuration management](#kustomize-kubernetes-native-configuration-management) - [Flagger](#flagger) - [WKSctl. Weave Kubernetes System Control](#wksctl-weave-kubernetes-system-control) - [Helm](#helm) - [Jenkins](#jenkins) - [Terraform](#terraform) - [Config Sync and Anthos Config Management](#config-sync-and-anthos-config-management) - [Portworx AutoPilot](#portworx-autopilot) - [OpenShift Applier](#openshift-applier) - [HashiCorp Waypoint](#hashicorp-waypoint) - [Weave GitOps](#weave-gitops) - [GitOps Frameworks](#gitops-frameworks) - [Kubernetes Platforms and GitOps](#kubernetes-platforms-and-gitops) - [OpenShift GitOps](#openshift-gitops) - [AWS Kubernetes](#aws-kubernetes) - [Weave Kubernetes Platform](#weave-kubernetes-platform) - [Ubuntu Charmed Kubernetes](#ubuntu-charmed-kubernetes) - [APIOps](#apiops) - [Images](#images) - [Tweets](#tweets) - [Videos](#videos) ## Introduction - [gitops.tech ๐ŸŒŸ](https://www.gitops.tech/) - [OpenGitOps ๐ŸŒŸ](https://opengitops.dev) OpenGitOps is a set of open-source standards, best practices, and community-focused education to help organizations adopt a structured, standardized approach to implementing GitOps. - [weave.works: Guide to GitOps](https://www.weave.works/technologies/gitops/) - [weave.works: What Is GitOps?](https://www.weave.works/blog/what-is-gitops-really) - [atlassian.com: Is GitOps the next big thing in DevOps?](https://www.atlassian.com/git/tutorials/gitops) - [cloudbees.com: What is GitOps?](https://www.cloudbees.com/gitops/what-is-gitops) - [dzone: What Is GitOps, Really?](https://dzone.com/articles/what-is-gitops-really) This article will help you understand what GitOps really is as a strategy for development, and its benefits over other CI/CD approaches - [Continuous GitOps, the way to do DevOps in Kubernetes](https://medium.com/@imarunrk/continuous-gitops-the-way-to-do-devops-in-kubernetes-896b0ea1d0fb) Continuous GitOps, the new age DevOps practice to increase the delivery velocity by achieving an end to end โ€œGit source of truthโ€ with Zero manual changes into the Kubernetes cluster. - [thenewstack.io: What Is GitOps and Why It Might Be The Next Big Thing for DevOps](https://thenewstack.io/what-is-gitops-and-why-it-might-be-the-next-big-thing-for-devops/) - [opensource.substack.com: All You Need To Know About GitOps](https://opensource.substack.com/p/all-you-need-to-know-about-gitops) A complete guide about GitOps, what why and how - [itnext.io: Continuous GitOps, the way to do DevOps in Kubernetes](https://itnext.io/continuous-gitops-the-way-to-do-devops-in-kubernetes-896b0ea1d0fb) Continuous GitOps, the new age DevOps practice to increase the delivery velocity by achieving an end to end โ€œGit source of truthโ€ with Zero manual changes into the Kubernetes cluster - [container-solutions.com: GitOps: The Bad and the Ugly](https://blog.container-solutions.com/gitops-the-bad-and-the-ugly) - [itnext.io: Principles, Patterns, and Practices for Effective Infrastructure as Code](https://itnext.io/principles-patterns-and-practices-for-effective-infrastructure-as-code-e5f7bbe13df1) Deliver Infrastructure and Software running on it Rapidly and Reliably at Scale. - [medium: GitOps: Build infrastructure resilient applications ๐ŸŒŸ](https://medium.com/@franoisdagostini/gitops-build-infrastructure-resilient-applications-95bbc939046d) - [itnext.io: Continuous GitOps, the way to do DevOps in Kubernetes ๐ŸŒŸ](https://itnext.io/continuous-gitops-the-way-to-do-devops-in-kubernetes-896b0ea1d0fb) Continuous GitOps, the new age DevOps practice to increase the delivery velocity by achieving an end to end โ€œGit source of truthโ€ with Zero manual changes into the Kubernetes cluster. - [itnext.io: Managing Kubernetes Secrets Securely with GitOps ๐ŸŒŸ](https://itnext.io/managing-kubernetes-secrets-securely-with-gitops-b8174b4f4d30) - [sufle.io: Adopting GitOps for Enhanced Operations](https://www.sufle.io/blog/adopting-gitops-for-enhanced-operations) - [medium: GitOps : The Next Big Thing for DevOps and Automation!](https://medium.com/searce/gitops-the-next-big-thing-for-devops-and-automation-2a9597e51559) If you have similar questions like: โ€œWhatโ€™s GitOps?โ€, โ€œWhy we are moving towards this?โ€, โ€œHow and when one can implement this strategy in now running environment?โ€, โ€œWhat are the tools it included?โ€ then you have landed on the right page. - [thenewstack.io: Understanding GitOps: The Latest Tools and Philosophies](https://thenewstack.io/understanding-gitops-the-latest-tools-and-philosophies/) - [samiyaakhtar.medium.com: GitOps Observability โ€” Visualizing the journey of a container](https://samiyaakhtar.medium.com/gitops-observability-visualizing-the-journey-of-a-container-5f6ef1f3c9d2) - [==clickittech.com: What is GitOps?== ๐ŸŒŸ](https://www.clickittech.com/devops/what-is-gitops) - [blog.container-solutions.com: 11 Reasons for Adopting GitOps](https://blog.container-solutions.com/why-adopt-gitops) - [==opensource.com: GitOps vs. DevOps: What's the difference?== ๐ŸŒŸ](https://opensource.com/article/21/3/gitops) Get to know GitOps, an evolved form of DevOps. | __Principle__ | __Focus__ | __Main Tool__ | __Other Tools__ | __Flexibility__ | __Correctness__ | | :---: | :---: | :---: | :---: | :---: | :---: | | __DevOps__ | Automation and frequent deployments | CI/CD pipeline | Supply chain management, Cloud Configuration as Code, etc. | Less strict and more open | Less focus on correctness | | __GitOps__ | Correctness; doing DevOps correctly | Git | Kubernetes, Controller (e.g., Operator), separate CI/CD pipelines, Infrastructure as a Code, etc. | Stricter and less open | Designed with correctness | - [geekflare.com: An Introduction to GitOps](https://geekflare.com/gitops-introduction/) - [thenewstack.io: GitOps Use Cases You May Not Have Considered](https://thenewstack.io/gitops-use-cases-you-may-not-have-considered/) - [kumomind.medium.com: Should I consider the GitOps methodology?](https://kumomind.medium.com/should-i-consider-the-gitops-methodology-f49e042b8c22) - [==dzone: GitOps: How to Ops Your Git the Right Way== ๐ŸŒŸ](https://dzone.com/articles/gitops-how-to-ops-your-git-the-right-way) In this article weโ€™ll look into the specifics of creating Git repositories structures โ€Šโ€” โ€Šthe very core of the GitOps approach. - [braindose.blog: 4 Key Characteristics for a Successful GitOps Implementation](https://braindose.blog/2020/03/18/4-key-characteristics-of-gitops/) - [blog.container-solutions.com: GitOps: The Bad and the Ugly](https://blog.container-solutions.com/gitops-limitations) - [cloudogu.com: GitOps in Software Development ๐ŸŒŸ](https://cloudogu.com/en/glossary/gitops/) - [gitops.tech: What is GitOps? ๐ŸŒŸ](https://www.gitops.tech/#tools) - [dzone: GitOps โ€“ DevOps for Infrastructure Automation ๐ŸŒŸ](https://dzone.com/articles/gitops-devops-for-infrastructure-automation) GitOps offers a way to automate and manage infrastructure by using proven DevOps best practices such as version control, code review, and CI/CD pipelines. - [unifiedguru.com: GitOps and the Cloud Operating Model โ€“ VMware Cloud Community ๐ŸŒŸ](https://www.unifiedguru.com/gitops-and-the-cloud-operating-model-vmware-cloud-community/) - [thenewstack.io: Misconfiguration Worries Grow](https://thenewstack.io/misconfiguration-worries-grow/) - [codefresh.io: The pains of GitOps 1.0 ๐ŸŒŸ](https://codefresh.io/devops/pains-gitops-1-0/) GitOps as a practice for releasing software has several advantages, but like all other solutions before it, has also several shortcomings. - [weave.works: Managing Kubernetes with GitOps in a multi-cluster, multi-cloud world](https://www.weave.works/blog/managing-kubernetes-with-gitops-in-a-multi-cluster-multi-cloud-world) - [viewnext.com: ยฟQuรฉ es GitOps?](https://www.viewnext.com/que-es-gitops/) - [thenewstack.io: Have Containers Will Travel: Why GitOps Is Essential for Multicloud ๐ŸŒŸ](https://thenewstack.io/have-containers-will-travel-why-gitops-is-essential-for-multicloud/) - [weave.works: Put Your Security Worries to Rest with GitOps Operational Control ๐ŸŒŸ](https://www.weave.works/use-cases/security-with-gitops/) GitOps workflows in the Weave Kubernetes Platform give teams a head start since they rely on Gitโ€™s strong correctness and security. Every pull request has a built-in and fully auditable trail. Many companies need to look beyond just compliance and seek a full GRC solution thatโ€™s integral to their workflows. - [thenewstack.io: Push vs. Pull in GitOps: Is There Really a Difference?](https://thenewstack.io/push-vs-pull-in-gitops-is-there-really-a-difference/) - [about.gitlab.com: 3 Ways to approach GitOps ๐ŸŒŸ](https://about.gitlab.com/blog/2021/04/27/gitops-done-3-ways/) - [developers.redhat.com: Why should developers care about GitOps?](https://developers.redhat.com/blog/2021/05/13/why-should-developers-care-about-gitops) - [openshift.com: Our Favorite Things from GitOps Con at KubeCon EU ๐ŸŒŸ](https://www.openshift.com/blog/our-favorite-things-from-gitops-con-at-kubecon-eu) - [devsecops.co.in: GitOps Guide โ€“ What, Why and How? ๐ŸŒŸ](https://devsecops.co.in/2021/05/13/gitops-guide-what-why-and-how/) - [en.sokube.ch: GitOps and the Millefeuille dilemma ๐ŸŒŸ](https://en.sokube.ch/post/gitops-and-the-millefeuille-dilemma-1) - [octopus.com: How to structure your Git repository for DevOps automation](https://octopus.com/blog/devops-automation-repo-design) - [testingclouds.wordpress.com: GitOps Demystified](https://testingclouds.wordpress.com/2021/06/02/gitops-demystified/) - [weave.works: Ops Automation - GitOps in the Modern Enterprise](https://www.weave.works/blog/gitops-in-the-modern-enterprise) - [openshift.com: What is GitOps? ๐ŸŒŸ](https://www.openshift.com/learn/topics/gitops/) While DevOps provides an agile team structure, GitOps is a framework to start executing on the vision. - [thenewstack.io: Security Will Be Instrumental for the Success of GitOps](https://thenewstack.io/security-will-be-instrumental-for-the-success-of-gitops/) - [weave.works: Thereโ€™s More to GitOps Than Meets the Eye](https://www.weave.works/blog/theres-more-to-gitops-than-meets-the-eye) - [solo.io: GlooOps: Progressive delivery, the GitOps way](https://www.solo.io/blog/glooops-progressive-delivery-the-gitops-way) - [go.weave.works: The GitOps Maturity Model - 4 evolutionary steps to continuous delivery (pdf)](https://go.weave.works/2021_GitOps_Maturity_Model.html) - [thenewstack.io: A Look at GitOps for the Modern Enterprise ๐ŸŒŸ](https://thenewstack.io/a-look-at-gitops-for-the-modern-enterprise/) - [shipa.io: GitOps in the enterprise ๐ŸŒŸ](https://www.shipa.io/innovation/gitops-in-the-enterprise/) - [itnext.io: GitOps with Kubernetes ๐ŸŒŸ](https://itnext.io/gitops-with-kubernetes-740f37ea015b) - [shipa.io: GitOps meets AppOps](https://www.shipa.io/innovation/gitops-meets-appops/) - [weave.works: Automating Kubernetes with GitOps (whitepaper) ๐ŸŒŸ](https://go.weave.works/automating-kubernetes-with-gitops-wp.html) - [devopslearners.com: What is GitOps?](https://devopslearners.com/what-is-gitops-168aac9a2ee) A small explanation for GitOps - [go.weave.works: The Practical Guide to GitOps (eBook)](https://go.weave.works/gitops-ebook.html) - [enterprisersproject.com: How to explain GitOps in plain English](https://enterprisersproject.com/article/2021/6/gitops-explained-plain-english) What is GitOps and why is it important? How can IT leaders explain GitOps to others, especially if they donโ€™t speak DevOps or cloud-native? Experts break it down - [redhat.com: An illustrated guide to GitOps](https://www.redhat.com/architect/illustrated-guide-gitops) Understanding the basic principles driving GitOps offers Enterprise Architects a new way of working in the modern enterprise. - [bunnyshell.com: GitOps vs. DevOps: Whatโ€™s the Difference? ๐ŸŒŸ](https://www.bunnyshell.com/blog/gitops-vs-devops) - [jimangel.io: Self-Updating GitOps](https://jimangel.io/post/auto-gitops-isitstillrunning.com/) Self-hosted, Self-healing, Self-updating, Self-patching Kubernetes madness - [stevesmith.tech: GitOps is a placebo](https://www.stevesmith.tech/blog/gitops-is-a-placebo/) - [weave.works: The History of GitOps ๐ŸŒŸ](https://www.weave.works/blog/the-history-of-gitops) - [opensource.com: How to get the most out of GitOps right now](https://opensource.com/article/21/8/gitops) GitOps is a great starting point to understand what is running in production, but it may need a little more augmentation to get it working just right for your engineering team. - [redhat.com: 3 rules for applying principles of GitOps to enterprise architecture](https://www.redhat.com/architect/3-gitops-rules-architecture) Check out these three rules for using GitOps to get your enterprise architecture up and running effectively. - [weave.works: Hardening Git for GitOps (white paper)](https://go.weave.works/hardening-git-for-gitops.html) - [magalix.com: GitOps 101: Whatโ€™s It All About?](https://www.magalix.com/blog/what-is-gitops) - [containerjournal.com: The 4 Levels of GitOps Maturity](https://containerjournal.com/features/the-4-levels-of-gitops-maturity/) - [thenewstack.io: How to Get the Most out of GitOps](https://thenewstack.io/how-to-get-the-most-out-of-gitops) **Just as Kubernetes was accepted as the best way to do cloud native applications, GitOps is gaining recognition as the best way to do Kubernetes.** - [weave.works: Case Study: National Australia Bank Decreases Operational Overhead with GitOps](https://www.weave.works/blog/case-study-national-australia-bank-decreases-operational-overhead-with-gitops) New case study on how GitOps helped NAB, Australia's largest business bank decrease operational overhead for their move to EKS: "We turned to Weaveworks because of their extensive EKS and Kubernetes experience, including their close partnership with AWS". - [betterprogramming.pub: How GitOps Can Help Prevent Security Misconfigurations](https://betterprogramming.pub/how-gitops-can-help-prevent-security-misconfigurations-8b506dcd89e1) Cloud-native development comes with its own set of security risks. Know how to tackle them - [blogs.sap.com: Decentralized GitOps over multiple environments](https://blogs.sap.com/2021/05/06/decentralized-gitops-over-environments/) - [thenewstack.io: Application Deployment Is Faster with GitOps](https://thenewstack.io/application-deployment-is-faster-with-gitops/) - [As an ops engineer not too familiar with Git, you just need to know 6 commands](https://twitter.com/janakiramm) - git init, git add, git commit, git status, git log, git revert - to harness the power of GitOps. - [thenewstack.io: Wait, Do We Need to Hold Up on GitOps?](https://thenewstack.io/wait-do-we-need-to-hold-up-on-gitops/) - [redhat.com: How to use GitOps in your enterprise architecture strategy ๐ŸŒŸ](https://www.redhat.com/architect/understanding-gitops) Understanding the four guiding principles is like runway lighting for implementing GitOps in your enterprise. - [codefresh.io: The pains of GitOps 1.0](https://codefresh.io/about-gitops/pains-gitops-1-0/) GitOps as a practice for releasing software has several advantages, but like all other solutions before it, has also several shortcomings. It seems that the honeymoon period is now over, and we can finally talk about the issues of GitOps (and the current generation of GitOps tools) - [==thenewstack.io: CNCF Working Group Sets Some Standards for โ€˜GitOpsโ€™==](https://thenewstack.io/cncf-working-group-sets-some-standards-for-gitops/) GitOps must meet these four requirements: 1. **Declarative:** A system managed by GitOps must have its desired state expressed declaratively. โ€œYouโ€™re no longer giving instructions, youโ€™re describing state,โ€ Murillo described. 2. **Versioned and Immutable:** Desired state is stored in a way that enforces immutability, versioning and retains a complete version history. โ€œThe only way for you to introduce change in your system is by creating a new version of your desired state,โ€™ Murillo added. 3. **Pulled Automatically:** Software agents automatically pull the desired state declarations from the source. Agents within the system pull the desired state from the repository. 4. **Continuously Reconciled:** Software agents continuously observe the actual system state and attempt to apply the desired state. โ€œThe desired state [of the system or software] is continually reconciled, Murillo said. - [thenewstack.io: GitOps and the Cheap Cloud Myth](https://thenewstack.io/repatriation-or-cloud-what-we-need-is-control/) - [==redhat.com: Comparing GitOps implementation patterns: Pros and cons==](https://www.redhat.com/architect/gitops-implementation-patterns) The CI/CD Controller pattern and the SCM Controller pattern take different approaches to automating application deployment from source code management. - [==developer.ibm.com: GitOps: Best practices for the real world==](https://developer.ibm.com/blogs/gitops-best-practices-for-the-real-world) - [chrisshort.net: GitOps: An implementation of DevOps (abstracts)](https://chrisshort.net/abstracts/gitops-implementation-devops/) - [==chrisshort.net: GitOps: An implementation of DevOps==](https://chrisshort.net/gitops-an-implementation-of-devops/) GitOps is a prescriptive way of implementing DevOps. You will not succeed in using GitOps if you haven't embraced some DevOps philosophies along the way. - [thenewstack.io: Trusted Delivery: Policy-Based Compliance the GitOps Way](https://thenewstack.io/trusted-delivery-policy-based-compliance-the-gitops-way/) - [thenewstack.io: Getting Started with GitOps ](https://thenewstack.io/getting-started-with-gitops/) - [==medium: Stop Using Branches for Deploying to Different GitOps Environments | ostis Kapelonis==](https://medium.com/containers-101/stop-using-branches-for-deploying-to-different-gitops-environments-7111d0632402) - [codefresh.io: Stop Using Branches for Deploying to Different GitOps Environments](https://codefresh.io/about-gitops/branches-gitops-environments) - **The question of "How do I promote a release to the next environment?" is becoming increasingly popular among organizations that want to adopt GitOps. You should NOT use Git branches for modelling different environments.** - [codefresh.io: The pains of GitOps 1.0](https://codefresh.io/about-gitops/pains-gitops-1-0/) - [==thenewstack.io: Can You GitOps Your APIs?==](https://thenewstack.io/can-you-gitops-your-apis/) - [weave.works: GitOps takes DevOps teams to higher levels of maturity](https://www.weave.works/blog/gitops-takes-devops-teams-to-higher-levels-of-maturity) - [==linkedin.com pulse: WTH is GitOps? | Pavan Belagatti==](https://www.linkedin.com/pulse/wth-gitops-pavan-belagatti/) - [medium.com/@buraktahtacioglu: GitOps Fundamentals โ€” CNCF Roadmap](https://medium.com/@buraktahtacioglu/gitops-fundamentals-cncf-roadmap-fa686dbced9d) GitOps deployments: - A GitOps agent is deployed on the cluster. - The GitOps agent is monitoring one or more Git repositories that define applications and contain Kubernetes manifests (or Helm charts or Kustomize files). - [toolbox.com: Why Are Organizations Adopting GitOps for Continuous Deployment in 2022?](https://www.toolbox.com/tech/devops/articles/more-organizations-adopting-gitops) GitOps extracts best practices of DevOps and utilizes software development methods like version control, code review, and CI/CD pipelines. But is it a sustainable approach? Hereโ€™s a look at its pros and cons. - [weave.works: The worldโ€™s largest telcos are now embracing GitOps. Deutsche Telekom explains why](https://www.weave.works/blog/deutsche-telekom-explain-why-they-chose-gitops-for-5g) GitOps and 5G - a deep dive into Deutsche Telekomโ€™s experience - [==thenewstack.io: Kubernetes at Scale without GitOps Is a Bad Idea==](https://thenewstack.io/kubernetes-at-scale-without-gitops-is-a-bad-idea/) - [harness.io: GitOps: The New Kid On The DevOps Block!](https://harness.io/blog/devops/gitops-new-kid-devops-block) GitOps: the single source of truth, the evangelizer of as-code, and the bringer of CI/CD automation. Get an intro view into GitOps here! - [==Dzone: 3 Steps to Developing a Successful GitOps Model==](https://dzone.com/articles/3-steps-to-developing-a-successful-gitops-model) **In this post, explore how GitOps best serves organizations that develop cloud-native solutions based on containerization and microservices.** - [linkedin pulse: GitOps vs. DevOps! | Pavan Belagatti](https://www.linkedin.com/pulse/gitops-vs-devops-pavan-belagatti/) - [==containerjournal.com: GitOps Workflows and Principles for Kubernetes==](https://containerjournal.com/features/gitops-workflows-and-principles-for-kubernetes/) - [harness.io: 6 Actionable GitOps Best Practices To Help You Get Started](https://harness.io/blog/devops/6-gitops-best-practices/) - [==codefresh.io: How to Model Your Gitops Environments and Promote Releases between Them== ๐ŸŒŸ](https://codefresh.io/blog/how-to-model-your-gitops-environments-and-promote-releases-between-them/) In this article, you'll learn how to use different folders on the same Git branch. Two questions after adopting GitOps are: - How should I represent different environments on Git? - How should I handle promoting releases between them? - [==piotrminkowski.com: Continuous Development on Kubernetes with GitOps Approach== ๐ŸŒŸ](https://piotrminkowski.com/2022/06/06/continuous-development-on-kubernetes-with-gitops-approach/) - [==harness.io: Managing the 'Git' in 'GitOps': 4 Ways to Structure Code in Your GitOps Repos== ๐ŸŒŸ](https://harness.io/blog/gitops-repo-structure) Declarative, immutable, and continuously reconciled infrastructure brings many benefits when managed through GitOps best practices. Here are four approaches to managing code used in those pipelines. - Application and Infrastructure Code in One Repository - Separate Infrastructure Repository, Multiple Branches - Separate Infrastructure Repository, Directory-Based - Multiple Infrastructure Repositories, One per Environment - [medium.com/codex: Points to Consider for Structuring Infrastructure as Code Repositories](https://medium.com/codex/points-to-consider-for-structuring-infrastructure-as-code-repositories-886ff58404b8)
[![gitops in a nutshell](images/GitOps-in-a-nutshell.png)](https://www.unifiedguru.com/gitops-and-the-cloud-operating-model-vmware-cloud-community/)
[![app ops](images/appops.png)](https://www.shipa.io/innovation/gitops-in-the-enterprise/)
## GitOps Working Group - [GitOps Working Group ๐ŸŒŸ](https://github.com/gitops-working-group/gitops-working-group) - The Five GitOps Principles (as defined by the GitOps Working Group) to the lifecycle of an infrastructure resource, like a virtual machine or load balancer: - Declarative Configuration (define the resource as code) - Version controlled (use source control to manage the resource definition) - Automated delivery (provision and manage the resource from the definition using automation) - Software Agents (implement automated configuration management for the resource) - Closed loop (build the delivery pipeline for integration testing for resource changes) ## Git Repositories Structures - [==dzone: GitOps: How to Ops Your Git the Right Way== ๐ŸŒŸ](https://dzone.com/articles/gitops-how-to-ops-your-git-the-right-way) In this article weโ€™ll look into the specifics of creating Git repositories structures โ€Šโ€” โ€Šthe very core of the GitOps approach. - [==codefresh.io: Stop Using Branches for Deploying to Different GitOps Environments==](https://codefresh.io/about-gitops/branches-gitops-environments/) How do I promote a release to the next environment? **You should NOT use Git branches for modeling different environments. If the Git repository holding your configuration (manifests/templates in the case of Kubernetes) has branches named โ€œstagingโ€, โ€œQAโ€, โ€œProductionโ€ and so on, then you have fallen into a trap.** Using branches for different environments should only be applied to legacy applications. - [==developers.redhat.com: Git best practices: Workflows for GitOps deployments== ๐ŸŒŸ](https://developers.redhat.com/articles/2022/07/20/git-workflows-best-practices-gitops-deployments) - Separate your repositories - Separate development in directories, not branches - Trunk-based development - Pay attention to policies and security ## GitOps Tools - [FluxCD, ArgoCD or Jenkins X: Which Is the Right GitOps Tool for You?](https://blog.container-solutions.com/fluxcd-argocd-or-jenkins-x-which-is-the-right-gitops-tool-for-you) - [slideshare: GitOps, Jenkins X & Future of CI/CD](https://slideshare.net/rakutentech/gitops-jenkins-x-future-of-cicd) - [kubesandclouds.com: Werf: Fully customizable GitOps](https://kubesandclouds.com/index.php/2020/09/01/werf-gitops/) - [searchitoperations.techtarget.com: GitOps pros grapple with Kubernetes configuration management. GitOps users seek ideal Kubernetes config tool ๐ŸŒŸ](https://searchitoperations.techtarget.com/news/252492459/GitOps-pros-grapple-with-Kubernetes-configuration-management) Configuration management challenges GitOps early adopters, especially at large enterprises with millions of lines of Kubernetes YAML to manage. Ultimately, the industry hasn't found an ideal approach to Kubernetes configuration management, especially for GitOps. - [Tanka](https://tanka.dev/tutorial/jsonnet) a utility that blends Helm charts with Jsonnet, which combines the deployment speed and ubiquity of Helm charts with the more granular customizability supported by Jsonnet. - [openshift.com: Announcing OpenShift GitOps](https://www.openshift.com/blog/announcing-openshift-gitops) - [ibm.com: Enable GitOps](https://www.ibm.com/garage/method/practices/run/gitops/) GitOps focuses on the Ops side of DevOps and shows how operations configurations, infrastructures, and actions are like software. Everything is code and code is managed with Git. - [openshift.com: OpenShift Pipelines and OpenShift GitOps are now Generally Available ๐ŸŒŸ](https://www.openshift.com/blog/openshift-pipelines-and-openshift-gitops-are-now-generally-available) - [weave.works: Weave Kubernetes Platform (WKP) Unlocks Cross Team Collaboration with Workspaces](https://www.weave.works/blog/wkp-team-workspaces-rbac) - [blog.container-solutions.com: FluxCD, ArgoCD or Jenkins X: Which Is the Right GitOps Tool for You? ๐ŸŒŸ](https://blog.container-solutions.com/fluxcd-argocd-jenkins-x-gitops-tools) - [cloudogu.com: Automation Assistants: GitOps tools in comparison ๐ŸŒŸ](https://cloudogu.com/en/blog/gitops-tools) - [shipa.io: From Terraform to GitOps to Pulumi ๐ŸŒŸ](https://shipa.io/2021/10/from-terraform-to-gitops-to-pulumi/) - [==vimeo.com: Weaveworks - Hybrid and Multi-Cloud Strategies for Kubernetes with GitOps==](https://vimeo.com/516520492) One of the biggest advantages Kubernetes has to offer is that it is agnostic to infrastructure and capable of managing diverse workloads running on different compute resources. This allows organizations to manage multiple developer platforms, who can operate across many environments such as on premise, hybrid and multiple clouds. - Streamlined processes and automation is pivotal for operations when managing clusters at scale and maintaining security and policy checks. Paul Curtis, Principal Solutions Architect will demonstrate GitOps and Weave Kubernetes Platform in a hybrid and multi-cloud setup. - Learn how to: - Use model-driven automation to increases reliability and stability across environments - Simplify multi-cluster management with GitOps - Enable developers to push code to production daily (self-service) - Improve utilization and capacity management through Kubernetes platforms on cloud and on-premise infrastructure
[![gitops pipeline](images/gitops-pipeline.png)](https://www.unifiedguru.com/gitops-and-the-cloud-operating-model-vmware-cloud-community/)
### Flux. The GitOps Operator for Kubernetes - [Flux. The GitOps operator for Kubernetes](flux.md) ### Kustomize. Kubernetes native configuration management - [kustomize.io ๐ŸŒŸ](https://kustomize.io/) - Kustomize introduces a template-free way to customize application configuration that simplifies the use of off-the-shelf applications. Now, built into kubectl as apply -k. - Kustomize traverses a Kubernetes manifest to add, remove or update configuration options without forking. - **It is available both as a standalone binary and as a native feature of kubectl.** - [nakamasato.medium.com: Comparison between Helm and Kustomize for Kubernetes yaml management](https://nakamasato.medium.com/comparison-between-helm-and-kustomize-for-kubernetes-yaml-management-aed32cef2627) - [pauldally.medium.com: Kustomize Best Practices (Part 1)](https://pauldally.medium.com/kustomize-best-practices-part-1-86f9f22d2f20) Kubectl includes a very useful command called kustomize that allows a template-free way to customize Kubernetes application configuration. - [pauldally.medium.com: Kustomize Best Practices (Part 2)](https://pauldally.medium.com/kustomize-best-practices-part-2-c560f1fa1409) - [notmattlucas.com: Kubernetes Configuration with Kustomize](https://notmattlucas.com/kubernetes-configuration-with-kustomize-f4dbba250f3) - [medium.com/@nanditasahu031: How to Start with Kustomize โ€” itโ€™s Features](https://medium.com/@nanditasahu031/how-to-start-with-kustomize-its-features-dd541c3d2fa8) ### Flagger - [Flagger](https://flagger.app/) Progressive Delivery Operator for Kubernetes. Release new versions of your application/services to Kubernetes like a pro with Weaveworks's Flagger. - [partlycloudy.blog: Release to Kubernetes like a Pro with Flagger](https://partlycloudy.blog/2020/07/08/release-to-k8s-like-a-pro-with-flagger/) ### WKSctl. Weave Kubernetes System Control * [Weave Kubernetes System Control - wksctl](https://github.com/weaveworks/wksctl) Open Source Weaveworks Kubernetes System * [WKSctl - A New OSS Kubernetes Manager using GitOps](https://www.weave.works/blog/wksctl-a-new-oss-kubernetes-manager-using-gitops) * [WKSctl: a Tool for Kubernetes Cluster Management Using GitOps](https://www.infoq.com/news/2020/02/wksctl-kubernetes-gitops/) ### Helm * [dzone: managing helm releases the gitops way](https://dzone.com/articles/managing-helm-releases-the-gitops-way) ### Jenkins - There are many tools in the market that have been technically built for GitOps, like [ArgoCD](https://argoproj.github.io/argo-cd/), [Flux](https://github.com/fluxcd/flux), and [Jenkins X](https://jenkins-x.io/). All these tools have in-built proficiency to implement GitOps process for you. But we are going to use our old beloved Jenkins. - [GitOps for Kubernetes with Jenkins](https://medium.com/stakater/gitops-for-kubernetes-with-jenkins-7db6304216e0) - [github.com/stakater/Xposer](https://github.com/stakater/Xposer) (with fabric8 java client library for kubernetes) - [GitOps with Jenkins and Kubernetes](https://medium.com/@abhishekbhardwaj510/gitops-with-jenkins-and-kubernetes-c20425244c73) - [github.com: Opstree-Go-WebApp](https://github.com/opstree/Opstree-Go-WebApp) A loaded GoLang app to do various DevOps POC's - [opstree.github.io](https://opstree.github.io/) ### Terraform - [How to Create a GitOps Workflow with Terraform and Jenkins](https://www.hashicorp.com/resources/how-create-gitops-workflow-terraform-jenkins/) ### Config Sync and Anthos Config Management - [Config Sync](https://cloud.google.com/kubernetes-engine/docs/add-on/config-sync/overview) - [Anthos Config Management](https://cloud.google.com/anthos/config-management) - Google built a tool called [Config Sync](https://cloud.google.com/kubernetes-engine/docs/add-on/config-sync/overview) which acts as the bridge between an external source code repository and the Kubernetes API server. [Anthos Config Management](https://cloud.google.com/anthos/config-management) is based on Config Sync to extend it to multicluster scenarios. ### Portworx AutoPilot - [Portworx AutoPilot](https://docs.portworx.com/portworx-install-with-kubernetes/autopilot/) - [portworx.com: Automating Kubernetes Data Management with GitOps & AutoPilot](https://portworx.com/automating-kubernetes-data-management-with-gitops-autopilot) ### OpenShift Applier - [openshift-applier](https://github.com/redhat-cop/openshift-applier) - [dzone: GitOps With OpenShift Applier ๐ŸŒŸ](https://dzone.com/articles/gitops-with-openshift-applier) GitOps in short is a set of practices to use Git pull requests to manage infrastructure and application configurations. ### HashiCorp Waypoint - [waypointproject.io](https://www.waypointproject.io/) Waypoint provides a modern workflow to build, deploy, and release across platforms. Waypoint uses a single configuration file and common workflow to manage and observe deployments across platforms such as Kubernetes, Nomad, EC2, Google Cloud Run, and more. - [hashicorp.com: Using Waypoint Runners To Enable GitOps Workflows](https://www.hashicorp.com/blog/using-waypoint-runners-to-enable-gitops-workflows) Waypoint runners perform builds, deployments, poll for Git repository changes, and allow deployments for any platform. ### Weave GitOps - [Weave GitOps Enterprise](https://www.weave.works/product/gitops-enterprise/) - Weave GitOps Enterprise is a continuous operations product that makes it easy to deploy and manage Kubernetes clusters and applications in any environment. With a single management console that lets you operate clusters running anywhere, in the public cloud, on the edge or in any hybrid scenario. Strong multi-tenancy can accelerate app delivery by providing developers with self-serve isolated workload namespaces across environments. - With Weave GitOps Enterprise, every change is recorded in Git โ€“ whether it's a change to application code or platform config and whoever was responsible. So you have a self-generating audit trail available at all times, and far fewer... - [thenewstack.io: Weave GitOps Core Integrates Git with Kubernetes ](https://thenewstack.io/weave-gitops-core-integrates-git-with-kubernetes/) - [thenewstack.io: Weave GitOps Trusted Delivery: A Road to Kubernetes Sanity?](https://thenewstack.io/weave-gitops-trusted-delivery-a-road-to-kubernetes-sanity/) ## GitOps Frameworks - [dzone: Why Now Is the Time for the Spring Boot of Infrastructure Automation ๐ŸŒŸ](https://dzone.com/articles/why-now-is-the-time-for-the-spring-boot-of-infrast) Application teams move fast using frameworks built to boost developer productivity. Learn how a productivity framework can help your DevOps initiative succeed. - [Kubestack ๐ŸŒŸ](https://www.kubestack.com/): [Doc:](https://www.kubestack.com/framework/documentation) Kubestack is an open-source GitOps framework for infrastructure automation built on Terraform and Kustomize. Itโ€™s designed for teams that want to automate Kubernetes based infrastructure and not reinvent automation. Think of it this way, Kubestack is to Terraform and infrastructure automation, what Spring Boot is to Java and cloud native applications. The framework supports all three major cloud providers and has been used as the foundation for a number of real world customer projects as part of my colleaguesโ€™ and my consulting work. It is fully documented, has a step-by-step tutorial to help users get started and even includes a local [GitOps development lab](https://www.kubestack.com/framework/documentation/tutorial-build-local-lab). So you can test-drive Kubestack and learn more about GitOps for infrastructure automation in the comfort of your own localhost. - [thenewstack.io: KubeStack: Towards Full-Stack GitOps](https://thenewstack.io/kubestack-towards-full-stack-gitops/) ## Kubernetes Platforms and GitOps ### OpenShift GitOps * [blog.openshift.com: Introduction to GitOps with OpenShift](https://blog.openshift.comintroduction-to-gitops-with-openshift/) * [learn.openshift.com: GitOps introduction](https://learn.openshift.com/introduction/gitops-introduction/) * [blog.openshift.com: is it too late to integrate GitOps?](https://blog.openshift.comis-it-too-late-to-integrate-gitops/) * [blog.openshift.com: OpenShift Authentication Integration with ArgoCD](https://blogopenshift.com/openshift-authentication-integration-with-argocd/) * [openshift.com: From Code to Production with GitOps, Tekton and ArgoCD](https://www.openshift.com/blog/from-code-to-production-with-gitops) * [medium: GitOps with Istio, Tekton and Argo CD โ€” on OpenShift 4](https://medium.com/@joelkaplan1/gitops-with-istio-tekton-and-argo-cd-on-openshift-4-5e42d22994e3) * [thenewstack.io: Red Hat Delivers Full GitOps CI/CD Built on Tekton and Argo](https://thenewstack.io/red-hat-delivers-full-gitops-ci-cd-built-on-tekton-and-argo/) * [redhat.com: Red Hat Makes DevOps a Reality with OpenShift GitOps and OpenShift Pipelines ๐ŸŒŸ](https://www.redhat.com/en/about/press-releases/red-hat-makes-devops-reality-openshift-gitops-and-openshift-pipelines) New Red Hat OpenShift features provide fully-integrated CI/CD pipeline for organizations to deliver applications more consistently and with greater predictability across the open hybrid cloud. ### AWS Kubernetes * [info.acloud.guru: Adopting GitOps for Kubernetes on AWS](https://info.acloud.guru/resources/deploying-kubernetes-with-gitops) ### Weave Kubernetes Platform * [weave.works: Weave Kubernetes Platform](https://www.weave.works/) Automate Enterprise Kubernetes the GitOps way * [github: Weave Net - Weaving Containers into Applications](https://github.com/weaveworks/weave) ### Ubuntu Charmed Kubernetes * [Charmed Kubernetes](https://ubuntu.com/kubernetes/features) * [Kubernetes GitOps with Azure Arc and Charmed Kubernetes](https://ubuntu.com/blog/gitops-with-azure-arc-and-charmed-kubernetes) ## APIOps - [betterprogramming.pub: Applying DevOps to API Development for APIOps](https://betterprogramming.pub/applying-devops-to-api-development-for-apiops-21e2e605333e) **DevOps + GitOps = APIOps** ## Images ??? note "Click to expand!"
[![traditional devops vs gitops](images/traditional_ops_vs_gitops.png)](https://www.linkedin.com/pulse/wth-gitops-pavan-belagatti/) [![devops pipeline vs gitops pipeline](images/devops_pipeline_vs_gitops_pipeline.png)](https://www.linkedin.com/pulse/wth-gitops-pavan-belagatti/)
## Tweets
Click to expand!
## Videos
Click to expand!

Hybrid and Multi-Cloud Strategies for Kubernetes with GitOps from Weaveworks on Vimeo.