Amazon EKS Capability for Argo CD now supports custom configuration
Amazon EKS now allows custom configuration for its Argo CD GitOps capability via a standard ConfigMap, enabling teams to tailor health checks and UI settings for managed clusters.
Amazon Web Services has expanded the Amazon EKS Capability for Argo CD to support custom configuration through a standard argocd-cm ConfigMap within clusters. This update enhances the managed GitOps continuous delivery experience by allowing administrators to adjust settings to align with team workflows. Users can now define custom health checks for Custom Resources, modify Argo CD UI banner content, and configure resource monitoring behaviors directly within the managed capability.
Cluster administrators gain greater control over application health reporting, addressing a limitation where default Argo CD health logic could inaccurately mark resources as healthy during provisioning. Custom health checks enable precise tracking, such as holding an Application at progressing until a database is fully ready. The capability also includes pre-built health checks for AWS Controllers for Kubernetes (ACK) and kro (Kube Resource Orchestrator) resources, ensuring accurate status reporting without additional setup.
The custom configuration feature is available in all AWS Regions where the EKS Capability for Argo CD is supported. Administrators can apply these settings using the same methods as upstream Argo CD, with AWS managing the implementation within the managed capability. This integration maintains consistency with standard Argo CD practices while extending functionality for EKS environments.
To implement custom configurations, users should refer to the Amazon EKS User Guide for guidance on configuring Argo CD settings. The documentation outlines steps for defining health checks, adjusting UI elements, and managing resource comparisons, ensuring teams can optimize the GitOps workflow for their specific operational needs.