ivampiresp/longhorn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Separate tls ingress option from secure backend

Browse Source 
Signed-off-by: Łukasz Sowa <lukasz@owlsome.dev>
This commit is contained in:
Łukasz Sowa 2022-05-27 17:59:22 +02:00 committed by David Ko
parent 368d8363da
commit fe5565dbcf
2 changed files with 4 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

@ -11,7 +11,7 @@ metadata:
labels: {{- include "longhorn.labels" . | nindent 4 }} labels: {{- include "longhorn.labels" . | nindent 4 }}
app: longhorn-ingress app: longhorn-ingress
annotations: annotations:
{{- if .Values.ingress.tls }} {{- if .Values.ingress.secureBackends }}
ingress.kubernetes.io/secure-backends: "true" ingress.kubernetes.io/secure-backends: "true"
{{- end }} {{- end }}
{{- range $key, $value := .Values.ingress.annotations }} {{- range $key, $value := .Values.ingress.annotations }}

4
chart/values.yaml
View File

@ -194,9 +194,11 @@ ingress:
host: sslip.io host: sslip.io
## Set this to true in order to enable TLS on the ingress record ## Set this to true in order to enable TLS on the ingress record
## A side effect of this will be that the backend service will be connected at port 443
tls: false tls: false
## Enable this in order to enable that the backend service will be connected at port 443
secureBackends: false
## If TLS is set to true, you must declare what secret will store the key/certificate for TLS ## If TLS is set to true, you must declare what secret will store the key/certificate for TLS
tlsSecret: longhorn.local-tls tlsSecret: longhorn.local-tls