argocd-internal-ingress.yaml
No OneTemporary
Actions

Size

820 B

Subscribers

None

argocd-internal-ingress.yaml
View Options

	apiVersion: networking.k8s.io/v1
	kind: Ingress
	metadata:
	name: argocd-internal-ingress
	namespace: argocd
	annotations:
	#cert-manager.io/cluster-issuer: letsencrypt-prod
	kubernetes.io/ingress.class: nginx
	kubernetes.io/tls-acme: "true"
	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"
	nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
	spec:
	rules:
	- host: argocd.internal.admin.swh.network
	http:
	paths:
	- path: /
	pathType: Prefix
	backend:
	service:
	name: argocd-server
	port:
	name: https