fix: allowed disabling the default service for more complex use-cases

Quickfix for vernemq#274
JeremyTheocharis · Sep 29, 2021 · 4b6958d · 4b6958d
1 parent 8c30c0a
commit 4b6958d
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 0 deletions.
diff --git a/helm/vernemq/templates/service.yaml b/helm/vernemq/templates/service.yaml
@@ -1,3 +1,4 @@
+{{- if .Values.service.enabled -}}
 apiVersion: v1
 kind: Service
 metadata:
@@ -82,3 +83,4 @@ spec:
   selector:
     app.kubernetes.io/name: {{ include "vernemq.name" . }}
     app.kubernetes.io/instance: {{ .Release.Name }}
+{{- end }}
diff --git a/helm/vernemq/values.yaml b/helm/vernemq/values.yaml
@@ -18,6 +18,8 @@ serviceMonitor:
   labels: {}
 
 service:
+  # Can be disabled if more advanced use cases require more complex setups, e.g., combining LoadBalancer and ClusterIP for internal and external access. See also issue #274.
+  enabled: true
   # NodePort - Listen to a port on nodes and forward to the service.
   # ClusterIP - Listen on the service internal to the cluster only.
   # LoadBalancer - Create a LoadBalancer in the cloud provider and forward to the service.