mirror of
https://github.com/rubenhensen/k8scd.git
synced 2026-11-15 14:29:09 +01:00
Ruben Hensen
134774509d
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.
24 lines
686 B
YAML
24 lines
686 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
namespace: argocd
|
|
|
|
|
|
# additional resources like ingress rules, cluster and repository secrets.
|
|
resources:
|
|
- https://raw.githubusercontent.com/argoproj/argo-cd/refs/tags/v3.4.12/manifests/install.yaml
|
|
- ingress.yaml
|
|
- httproute.yaml
|
|
- oidc-secret.yaml
|
|
|
|
patches:
|
|
- target:
|
|
group: apps
|
|
version: v1
|
|
kind: ReplicaSet
|
|
name: argocd-notifications-controller
|
|
path: overlays/argocd-notifications-controller-patch.yaml
|
|
- path: overlays/argocd-cm.patch.yaml
|
|
- path: overlays/argocd-rbac-cm.patch.yaml
|
|
- path: overlays/argocd-cmd-params-cm.patch.yaml
|
|
- path: overlays/patched-ca-bundle.patch.yaml |