fix https backend for svc/argocd-server

This commit is contained in:
Aaron Riedel 2023-02-12 21:22:56 +01:00
parent fd60c22347
commit 230a20273c
Signed by: aaron
GPG key ID: 643004654D40D577
2 changed files with 4 additions and 1 deletions

View file

@ -7,8 +7,9 @@ metadata:
annotations: annotations:
kubernetes.io/ingress.class: "nginx" kubernetes.io/ingress.class: "nginx"
cert-manager.io/cluster-issuer: letsencrypt-prod cert-manager.io/cluster-issuer: letsencrypt-prod
acme.cert-manager.io/http01-edit-in-place: "true" acme.cert-manager.io/http01-edit-in-place: "false"
ingress.kubernetes.io/ssl-redirect: "false" ingress.kubernetes.io/ssl-redirect: "false"
nginx.org/ssl-services: "argocd-server"
spec: spec:
rules: rules:
- host: "argo.apps.yolokube.de" - host: "argo.apps.yolokube.de"

View file

@ -72,6 +72,8 @@ metadata:
cert-manager.io/cluster-issuer: letsencrypt-prod cert-manager.io/cluster-issuer: letsencrypt-prod
acme.cert-manager.io/http01-edit-in-place: "true" acme.cert-manager.io/http01-edit-in-place: "true"
ingress.kubernetes.io/ssl-redirect: "false" ingress.kubernetes.io/ssl-redirect: "false"
# Use the following annotation if the backend only speaks HTTPS (fill out the service name accordingly):
#nginx.org/ssl-services: "example-service"
spec: spec:
rules: rules:
- host: "example.apps.yolokube.de" - host: "example.apps.yolokube.de"