From 4b6958d01648c5fe994dd29736adbf5aa95bc101 Mon Sep 17 00:00:00 2001
From: jeremy Theocharis <jt@umh.app>
Date: Wed, 29 Sep 2021 18:17:56 +0200
Subject: [PATCH] fix: allowed disabling the default service for more complex
 use-cases

Quickfix for #274
---
 helm/vernemq/templates/service.yaml | 2 ++
 helm/vernemq/values.yaml            | 2 ++
 2 files changed, 4 insertions(+)

diff --git a/helm/vernemq/templates/service.yaml b/helm/vernemq/templates/service.yaml
index 4264acd..df8eac5 100644
--- 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
index 93ce31c..a93e863 100644
--- 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.