Skip to content

Mark Tailscale ingresses healthy in Argo #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
syscod3 merged 1 commit into from
Sep 6, 2026
Merged

Mark Tailscale ingresses healthy in Argo #73

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions bootstrap/argocd-cm.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,21 @@ data:
resource.customizations.ignoreDifferences.apps_Deployment: |
jsonPointers:
- /status/terminatingReplicas
# Tailscale publishes the external address outside Kubernetes. Its Ingress
# status therefore remains empty even when the endpoint is working.
resource.customizations.health.networking.k8s.io_Ingress: |
hs = {}
if obj.spec.ingressClassName == "tailscale" then
hs.status = "Healthy"
hs.message = "Tailscale owns the external endpoint"
elseif obj.status and obj.status.loadBalancer and obj.status.loadBalancer.ingress and #obj.status.loadBalancer.ingress > 0 then
hs.status = "Healthy"
hs.message = "Ingress has an external address"
else
hs.status = "Progressing"
hs.message = "Waiting for an external address"
end
return hs
resource.exclusions: |
# Keep Argo CD 3's default high-churn exclusions while preserving the
# pre-existing CiliumIdentity exclusion.
Expand Down
Loading