Files
k8scd/apps/templates/argocd-folder.yaml
T
Ruben Hensen 134774509d argocd: serve plain HTTP behind the ingress and the Gateway
With server.insecure, TLS ends at nginx or Envoy and argocd-server serves plain HTTP, which is how Argo CD documents the Gateway API setup. The nginx Ingress now talks HTTP to the http port; the ssl-passthrough annotation did nothing without the controller flag. argocd-folder diffs server-side for the new HTTPRoute.
2026-10-23 17:44:08 +02:00

25 lines
672 B
YAML

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: argocd-folder
annotations:
# Let the API server fill in Gateway API defaults before diffing.
argocd.argoproj.io/compare-options: ServerSideDiff=true
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: argocd
destination:
server: https://kubernetes.default.svc
namespace: argocd
syncPolicy:
syncOptions:
- CreateNamespace=true
# From Argo CD 3.3 the ApplicationSet CRD is too big for client-side
# apply's last-applied annotation.
- ServerSideApply=true
automated:
selfHeal: true