2024-04-22 00:14:48 +00:00
|
|
|
apiVersion: networking.k8s.io/v1
|
|
|
|
|
kind: Ingress
|
|
|
|
|
metadata:
|
|
|
|
|
name: argocd-server-ingress
|
|
|
|
|
namespace: argocd
|
|
|
|
|
annotations:
|
2024-04-22 15:57:57 +00:00
|
|
|
cert-manager.io/cluster-issuer: "letsencrypt-staging"
|
2024-04-22 00:14:48 +00:00
|
|
|
nginx.ingress.kubernetes.io/ssl-passthrough: "true"
|
|
|
|
|
# If you encounter a redirect loop or are getting a 307 response code
|
|
|
|
|
# then you need to force the nginx ingress to connect to the backend using HTTPS.
|
|
|
|
|
nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
|
|
|
|
|
spec:
|
|
|
|
|
ingressClassName: nginx
|
|
|
|
|
rules:
|
|
|
|
|
- host: argo.sbtp.xyz
|
|
|
|
|
http:
|
|
|
|
|
paths:
|
|
|
|
|
- path: /
|
|
|
|
|
pathType: Prefix
|
|
|
|
|
backend:
|
|
|
|
|
service:
|
|
|
|
|
name: argo-argocd-server
|
|
|
|
|
port:
|
|
|
|
|
name: https
|
|
|
|
|
tls:
|
|
|
|
|
- hosts:
|
|
|
|
|
- argo.sbtp.xyz
|
|
|
|
|
secretName: argocd-server-tls # as expected by argocd-server
|
