GitOps Engine

Two of the biggest GitOps projects are joining forces. Argo CD and Flux CD have been out there for years, making the lives of operators and organisations easier. Now the teams are building the best possible GitOps solution together. The first step on this journey is the GitOps Engine.

Argo and Flux already have similar sets of functionality, soon they will start sharing code using the GitOps Engine. The GitOps Engine will be responsible for the following functionality:

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

Over time, this might be useful to other projects too.

Proposals, specifications and ideas

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.

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 #gitops channel on Kubernetes Slack (get an invite here).

Slack Ask-Us-Anything

We tried to summarise all relevant information here on Github. There's still very likely something we missed or which might be unclear, so we thought we'd bring together everyone behind this in one place and host an ask-us-anything session, where you can dive right into the big questions and the nuts and bolts of this announcement together with us.

• When: 25th Nov 2019, 09:00 Pacific time (convert to your timezone here)
• Where: #gitops channel on Kubernetes Slack (get an invite here)

We're looking forward to seeing you there! Bring your friends and bring your questions!