fix(nextcloud): Don't require nodePort if none is specified #606

Don't require `nodePort` to template if none is specified
nextcloud · Sep 12, 2024 · fae58fe · fae58fe
2 parents 5381a62 + 6f25538
commit fae58fe
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git a/charts/nextcloud/Chart.yaml b/charts/nextcloud/Chart.yaml
@@ -1,6 +1,6 @@
 apiVersion: v2
 name: nextcloud
-version: 5.5.5
+version: 5.5.6
 appVersion: 29.0.6
 description: A file sharing server that puts the control and security of your own data back into your hands.
 keywords:

diff --git a/charts/nextcloud/templates/service.yaml b/charts/nextcloud/templates/service.yaml
@@ -32,10 +32,10 @@ spec:
       targetPort: {{ .Values.nextcloud.containerPort }}
       protocol: TCP
       name: http
-      {{- if (eq .Values.service.type "NodePort") }}
-      nodePort: {{ .Values.service.nodePort | default "" }}
+      {{- with .Values.service.nodePort }}
+      nodePort: {{ . }}
       {{- end }}
   selector:
     app.kubernetes.io/name: {{ include "nextcloud.name" . }}
     app.kubernetes.io/instance: {{ .Release.Name }}
-    app.kubernetes.io/component: app
+    app.kubernetes.io/component: app
diff --git a/charts/nextcloud/values.yaml b/charts/nextcloud/values.yaml
@@ -500,7 +500,7 @@ service:
   type: ClusterIP
   port: 8080
   loadBalancerIP: ""
-  nodePort: nil
+  nodePort:
   annotations: {}
     ## Insert your annotations such as below
     # test/test: pumuckel