Roadmap

Argo CD does not publish a dated feature roadmap. Minor versions ship on a fixed quarterly schedule, and a feature ships in the next minor release cut from master after it is merged. For larger features, maintainers may ask for a design document during triage.

The links below always show the current state of the project.

Upcoming releases

Release dates, release champions and release checklists are listed in the Release Process and Cadence document.

Items that maintainers have committed to review for a specific release are tracked in its GitHub milestone. The feature freeze starts with the first release candidate, seven weeks before general availability. Items that are not merged before the freeze should be moved to the next release's milestone.

Candidate breaking changes for v4.0

Breaking changes that cannot ship in a 3.x release are collected in the v4.0 milestone. Some of them are decided and some are still open questions. Review the milestone if you want to know which deprecated fields, flags and defaults may change.

Features under design

Enhancements that are complex enough to require a design document are labelled proposal:required. Design documents are discussed in open proposal pull requests, and accepted ones are stored in the docs/proposals directory.

Note

An accepted proposal is not a commitment to a release date. It is implemented when a contributor picks it up.

Most requested enhancements

See the most-upvoted open enhancement requests. Add a 👍 reaction to an issue to show that you need it. Avoid "+1" comments, since they notify every subscriber without adding information.

Released features

Each minor release is announced on the Argo Project blog and in the GitHub releases.

Influencing the direction of the project

To propose a new feature, open an enhancement proposal. To discuss priorities with the maintainers, add an item to the agenda of the contributor meeting.