Files
k8s-manifests/monitoring/ingress-uptime-kuma-redirect.yaml
T
chemavxandClaude Opus 4.8 e26b8b95ad monitoring: quitar last-applied-configuration de los manifiestos propios
Basura del volcado con kubectl get -o yaml. Al estar versionada se muerde la
cola: ArgoCD la aplica, k8s genera una nueva que ya incluye el tracking-id, y
git y cluster no coinciden nunca -> los 4 recursos se quedaban OutOfSync para
siempre. Verificado que el resto del manifiesto queda byte a byte igual.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-25 15:40:01 +00:00

28 lines
672 B
YAML

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
traefik.ingress.kubernetes.io/router.entrypoints: websecure
traefik.ingress.kubernetes.io/router.middlewares: monitoring-redirect-to-status@kubernetescrd
name: uptime-kuma-redirect
namespace: monitoring
spec:
ingressClassName: traefik
rules:
- host: uptime.chemavx.xyz
http:
paths:
- backend:
service:
name: uptime-kuma
port:
number: 3001
path: /
pathType: Prefix
tls:
- hosts:
- uptime.chemavx.xyz
secretName: uptime-kuma-redirect-tls