Adrian A. Baumann
3d9d01c240
- Add traefik-middleware.yaml with patch documentation - Add ARGOCD-INGRESS-FIX.md with complete explanation of the issue and solution - Traefik now reports Ingress status.loadBalancer IP to allow ArgoCD to assess Ingress health - Fixes: Django Ingress stuck in 'Progressing' state
25 lines
1.1 KiB
YAML
25 lines
1.1 KiB
YAML
---
|
|
# Traefik configuration to enable Ingress status updates
|
|
# This patch configures Traefik to report its IP address in Ingress.status.loadBalancer
|
|
# which is required for ArgoCD to properly assess Ingress health status
|
|
apiVersion: v1
|
|
kind: ConfigMap
|
|
metadata:
|
|
name: traefik-patch-note
|
|
namespace: traefik
|
|
annotations:
|
|
description: "Manual patch applied to traefik deployment to enable ingress status reporting"
|
|
data:
|
|
patch-command: |
|
|
kubectl patch deployment traefik -n traefik --type='json' \
|
|
-p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--providers.kubernetesingress.ingressendpoint.publishedservice=traefik/traefik"}]'
|
|
|
|
rationale: |
|
|
The Ingress resource needs its status.loadBalancer.ingress field populated for ArgoCD to assess health.
|
|
Without this, Ingress resources remain in "Progressing" state indefinitely.
|
|
|
|
This flag tells Traefik to:
|
|
- Monitor the specified Service (traefik/traefik - the LoadBalancer service)
|
|
- Automatically update Ingress.status.loadBalancer with the service's external IP
|
|
- Allow ArgoCD to transition the Ingress from "Progressing" to "Healthy"
|