Helm chart: option to provide different services for different ports

[tomasgareau]

Currently, the Helm chart for VerneMQ allows the user to select a Service type (.Values.service.type) and ports to expose through that service (.Values.service.mqtt, .Values.service.mqtts, etc.,). This service exposes all the ports with enabled: true under .Values.service.

It would be nice to be able to specify different service types for different ports. The use-case I have in mind would be:

• exposing MQTTS via a LoadBalancer service
• exposing MQTT via a ClusterIP service

That way, I can communicate externally with TLS/SSL, but use an unencrypted connection within my cluster. An added bonus would be making it easier to debug/view MQTT messages by kubectl port-forward'ing the MQTT ClusterIP service.

Alternatively, this is something I can do by manually creating a service after deployment:

apiVersion: v1
kind: Service
metadata:
  name: vernemq-plain
  namespace: default
spec:
  type: ClusterIP
  selector:
    app.kubernetes.io/instance: vernemq
    app.kubernetes.io/name: vernemq
  ports:
  - name: mqtt
    port: 1883
    protocol: TCP
    targetPort: mqtt

but I'd have to manually set the selector labels rather than having them filled out by templated values.

[JeremyTheocharis]

I have a similar issue: I want to have different ports, e.g., 1883 and 1884, for ClusterIP and LoadBalancer. I am currently creating a Pull Request, which allows at least to disable the standard service template.