Skip to content

argoproj/gitops-engine

Folders and files

NameName
Last commit message
Last commit date
Mar 4, 2025
Feb 7, 2025
Aug 25, 2020
Jun 28, 2024
Apr 20, 2021
Mar 27, 2025
Apr 12, 2022
Nov 26, 2024
Feb 7, 2025
Nov 26, 2024
Oct 3, 2019
Oct 27, 2020
Mar 15, 2021
Dec 12, 2024
May 18, 2020
Mar 13, 2025
Mar 13, 2025
Feb 27, 2025

Repository files navigation

GitOps Engine

Various GitOps operators address different use-cases and provide different user experiences but all have similar set of core features. The team behind Argo CD has implemented a reusable library that implements core GitOps features:

  • Kubernetes resource cache ✅
  • Resources reconciliation ✅
  • Sync Planning ✅
  • Access to Git repositories
  • Manifest Generation

Proposals, specifications and ideas

Do you want to propose one more feature and want to enhance the existing one? Proposals and ideas are in markdown docs in the specs/ directory. To create a new proposal, simply copy the spec template, name the file corresponding to the title of your proposal, and place it in the specs/ directory.

A good starting point to understand the structure is the GitOps Engine Design spec.

We tried to answer frequently asked question in a separate FAQ document.

Governance

This project is licensed under the Apache 2 license.

The GitOps Engine follows the CNCF Code of Conduct.

Get involved

If you are as excited about GitOps and one common engine for it as much as we are, please get in touch. If you want to write code that's great, if you want to share feedback, ideas and use-cases, that's great too.

Find us on the #argo-cd-contributors on CNCF Slack (get an invite here).

Contributing to the effort

At this stage we are interested in feedback, use-cases and help on the GitOps Engine.