From d138e5c4a031767c3d3d66229c5c1208ed0e3823 Mon Sep 17 00:00:00 2001 From: DeveloperDurp Date: Sat, 3 Dec 2022 05:47:19 -0600 Subject: [PATCH] ingress --- longhorn/values.yaml | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/longhorn/values.yaml b/longhorn/values.yaml index e7ea3b4..bdc360b 100644 --- a/longhorn/values.yaml +++ b/longhorn/values.yaml @@ -45,11 +45,11 @@ longhorn: loadBalancerSourceRanges: "" persistence: - defaultClass: true + defaultClass: false defaultFsType: ext4 - defaultClassReplicaCount: 3 + defaultClassReplicaCount: 1 defaultDataLocality: disabled # best-effort otherwise - reclaimPolicy: Delete + reclaimPolicy: Retain migratable: false recurringJobSelector: enable: false @@ -175,20 +175,23 @@ longhorn: ingress: ## Set to true to enable ingress record generation - enabled: false + enabled: true ## Add ingressClassName to the Ingress ## Can replace the kubernetes.io/ingress.class annotation on v1.18+ - ingressClassName: ~ + ingressClassName: nginx - host: sslip.io + host: longhorn.internal.durp.info ## 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: + - secretName: longhorn-tls + hosts: + - longhorn.internal.durp.info ## If TLS is set to true, you must declare what secret will store the key/certificate for TLS - tlsSecret: longhorn.local-tls + tlsSecret: longhorn-tls ## If ingress is enabled you can set the default ingress path ## then you can access the UI by using the following full path {{host}}+{{path}} @@ -203,8 +206,7 @@ longhorn: ## ## If tls is set to true, annotation ingress.kubernetes.io/secure-backends: "true" will automatically be set annotations: - # kubernetes.io/ingress.class: nginx - # kubernetes.io/tls-acme: true + cert-manager.io/cluster-issuer: letsencrypt-production secrets: ## If you're providing your own certificates, please use this to add the certificates as secrets