- v2.4 and beyond
- ✅ Config Management Tools Integrations (proposal)
- ✅ Argo CD Extensions (proposal)
- ✅ Project scoped repository and clusters (proposal)
- ✅ Core Argo CD (proposal)
- ✅ Core Functionality Bug Fixes
- ✅ Performance
- ✅ ApplicationSet
- ✅ Large Applications support
- ✅ Serviceability
- ✅ Argo CD Notifications
- ✅ Automated Registry Monitoring
- ✅ Projects Enhancements
Merge Argo CD Notifications into Argo CD¶
Input Forms UI Refresh¶
Improved design of the input forms in Argo CD Web UI: https://www.figma.com/file/IIlsFqqmM5UhqMVul9fQNq/Argo-CD?node-id=0%3A1
Compact resources tree¶
An ability to collaps leaf resources tree to improve visualization of very large applications: #7349
Maintain difference in cluster and git values for specific fields¶
The feature allows to avoid updating fields excluded from diffing (#2913).
Exec into the Kubernetes Pod right from Argo CD Web UI! #4351
Helm values from external repo¶
The feature allows combining of-the-shelf Helm chart and value file in Git repository (#2789)
v2.4 and beyond¶
Merge ApplicationSet controller into Argo CD¶
Merge Argo CD Image Updater into Argo CD¶
Config Management Tools Integrations UI/CLI¶
Allow specifying parent/child relationships in config¶
The feature #5082 allows configuring parent/child relationships between resources. This allows to correctly visualize custom resources that don't have owner references.
Dependencies between applications¶
The feature allows specifying dependencies between applications that allow orchestrating synchronization of multiple applications. #3517
GitOps Engine Enhancements¶
The GitOps Engine is a library that implements core GitOps functions such as K8S resource reconciliation and diffing. A lot of Argo CD features are still not available in GitOps engine. The following features have to be contributed to the GitOps Engine:
- an ability to customize resources health assessment and existing CRD health assessment functions.
- resource diffing customization.
- config management tools integration.
- unified syncing annotations argoproj/gitops-engine#43.
The community likes the first class support of Helm, Kustomize and keeps requesting support for more tools. Argo CD provides a mechanism to integrate with any config management tool. We need to investigate why it is not enough and implement missing features.
Argo CD supports customizing handling of Kubernetes resources via diffing customizations, health checks, and custom actions. The Argo CD Extensions proposal takes it to next level and allows to deliver the resource customizations along with custom visualization in Argo CD via Git repository.
The feature streamlines the process of adding repositories and clusters to the project and makes it self-service. Instead of asking an administrator to change Argo CD settings end users can perform the change independently.
Core Argo CD allows to installation and use of lightweight Argo CD that includes only the backend without exposing the API or UI. The Core Argo CD provides a better experience to users who need only core Argo CD features and don't want to deal with multi-tenancy features.
✅ Core Functionality Bug Fixes¶
The core GitOps features still have several known bugs and limitations. The full list is available in v1.9 milestone
The most notable issues:
2000+ Applications support. The user interface becomes notably slower if one Argo CD instance manages more than 1 thousand applications. A set of optimizations is required to fix that issue.
100+ Clusters support. The cluster addon management use-case requires connecting a large number of clusters to one Argo CD controller. Currently Argo CD controller is unable to handle that many clusters. The solution is to support horizontal controller scaling and automated sharding.
Mono Repository support. Argo CD is not optimized for mono repositories with a large number of applications. With 50+ applications in the same repository, manifest generation performance drops significantly. The repository server optimization is required to improve it.
Argo CD Applications allow splitting the cluster configuration into logic groups that are managed independently. However, the set of applications is a configuration that should be managed declaratively as well. The app-of-apps pattern solves this problem but still has some challenges such as maintenance overhead, security, and lack of some additional features.
ApplicationSet project provides a better solution for managing applications across multiple environments.
✅ Large Applications support¶
The application details page is not suitable to visualize applications that include a large number of resources (hundreds of resources). The page has to be reworked to improve user experience.
To make Argo CD successful we need to build tools that enable Argo CD administrators to handle scalability and performance issues in a self-service model.
That includes more metrics, out-of-the-box alerts and a cluster management user interface.
✅ Argo CD Notifications¶
Argo CD Notifications provides the ability to notify users about Argo CD Application changes as well as implement integrations such as update GitHub commit status, trigger Jenkins job, set Grafana label, etc.
✅ Automated Registry Monitoring¶
✅ Projects Enhancements¶
Argo CD projects accumulated a lot of debt:
- Users don't know how to use project roles and SSO. It is one of the key features but not documented well. We need to document and promote it
- Project management UI has evolved organically and needs a complete redesign. We packaged everything into one sliding panel which is painful to use
- Enhancements: #3598