tea/browsertrix
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

ingress: remove X-Forward-Proto snippet, no longer needed (and now possibly considered unsafe) (#2519)

Browse Source 
X-Forward-Proto is now already provided by the standard ingress-nginx config
This commit is contained in:
Ilya Kreymer 2025-03-25 17:24:55 -07:00 committed by GitHub
parent 21a372057b
commit 9250befea4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
chart/templates/ingress.yaml
View File

@ -18,8 +18,6 @@ metadata:
nginx.ingress.kubernetes.io/upstream-vhost: "{{ .Values.ingress.host }}" nginx.ingress.kubernetes.io/upstream-vhost: "{{ .Values.ingress.host }}"
{{- if .Values.ingress.tls }} {{- if .Values.ingress.tls }}
cert-manager.io/cluster-issuer: {{ .Values.ingress.custom_cluster_issuer | default "cert-main" }} cert-manager.io/cluster-issuer: {{ .Values.ingress.custom_cluster_issuer | default "cert-main" }}
nginx.ingress.kubernetes.io/configuration-snippet: |
proxy_set_header X-Forwarded-Proto {{ .Values.ingress.tls | ternary "https" "http" }};
nginx.ingress.kubernetes.io/ssl-redirect: "true" nginx.ingress.kubernetes.io/ssl-redirect: "true"
{{- else }} {{- else }}
nginx.ingress.kubernetes.io/ssl-redirect: "false" nginx.ingress.kubernetes.io/ssl-redirect: "false"