You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for i, condition in ipairs(obj.status.conditions) do
if condition.type == "Ready" and condition.status == "False" then
hs.status = "Degraded"
hs.message = condition.message
return hs
end
if condition.type == "Ready" and condition.status == "True" then
hs.status = "Healthy"
hs.message = condition.message
return hs
end
end
end
end
hs.status = "Progressing"
hs.message = "Waiting for certificate"
return hs
Example for Traefik IngressRoute:
data:
...resource.customizations.links.traefik.containo.us-IngressRoute |links = []// walk object and create link for each configured host and pathreturn links
Additional Requirements
It should be possible to create multiple links from one resource, as one IngressRoute can define multiple ingress rules.
Links should propagate up to the Application resource, like they do for core Ingress resources.
Summary
It should be possible for ArgoCD to display links for non-core ingress resources.
Motivation
Besides the Kubernetes-core resource
Ingress
, some applications come with CRDs, that define new ingress resources. OpenShiftRoute
(https://docs.openshift.com/container-platform/4.11/rest_api/network_apis/route-route-openshift-io-v1.html) and TraefikIngressRoute
(https://doc.traefik.io/traefik/providers/kubernetes-crd/) come to my mind. For OpenShift there is a (seems-to-be-abandoned) open PR #5096.Proposal
Links could be implemented the same way health checks are: Resource Customization.
Bundle Popular Resources with ArgoCD
Bundle more popular resources with ArgoCD natively, like we do it for health checks for some resources.
For example Prometheus:
argo-cd/resource_customizations/monitoring.coreos.com/Prometheus/health.lua
Lines 1 to 23 in 231fab4
We could put a
links.lua
in the same folder for links created forPrometheus
resources, for example.Read Link Customization from ArgoCD config
Provide a way to specify resource customization in the
argocd-cm.yaml
file.For example health checks for custom resources:
argo-cd/docs/operator-manual/argocd-cm.yaml
Lines 104 to 124 in 231fab4
Example for Traefik
IngressRoute
:Additional Requirements
IngressRoute
can define multiple ingress rules.Application
resource, like they do for coreIngress
resources.Releated Issues
The text was updated successfully, but these errors were encountered: