Open sbose78 opened 3 years ago
We've faced several health check issues after upgrading to v2.0: After https://github.com/argoproj/argo-cd/issues/6039 and https://github.com/argoproj/argo-cd/issues/6035. The fix requires Argo CD release although health check is just a Lua script.
At the same time, I really don't want to make Argo CD similar to Istio and ask users to install dozens of CRDs. What do you think about the following compromise solution:
HealthCheck
that "manages" resource keys in Argo CD ConfigMap. community-health-checks
and move built-in health checks This way we can keep the number of required CRDs small. If later we learn that everyone install HealthCheck
then we can merge it into Argo CD
What do you think @sbose78 ?
That sounds like a great approach!
@sbose78 we'd like to fold this into the Argo CD extensions proposal, which will replace current mechanism of health checks in the argocd configmap: https://github.com/argoproj/argo-cd/pull/6240
Thank you, I'll review it, Jesse!
Summary
Introduce a
HealthCheck
CRD for defining healthchecks for non-standard Kubernetes types ( and overrides to standard Kubernetes types). This would make custom health checks pluggable and more manage-able for a specific deployment of ArgoCDMotivation
argocd-cm
)Proposal
HealthCheck
CRD that would be used to declare the lua script for a specific "GroupVersionKind".argocd-cm.yaml
community-health-checks
where all health checks ( and their tests ) in https://github.com/argoproj/argo-cd/tree/master/resource_customizations would be migrated over asHealthCheck
CRs.