This article explains how to expose the HiveMQ Control Center and Rest API using Ingress.

For this you have to have a Kubernetes Ingress Controller of your choice (e.g. NGINX, Traefik, Voyager, …) already setup and running.

Architecture Overview

(Source: https://kubernetes.io/docs/concepts/services-networking/ingress/ )

Prepare your HiveMQ Deployment

To deploy HiveMQ in Kubernetes using helm you have to download the default values.yaml file from the official GitHub repository (https://github.com/hivemq/helm-charts/blob/master/charts/hivemq-operator/values.yaml) first.

After this you have to edit the file so the HiveMQ Control Center “cc” and the HiveMQ Rest API “api” will not get exposed (expose: false). You also have to uncomment the "api" section as you can see in the following example. With this configuration, the HiveMQ Kubernetes Operator will not create Kubernetes Services for these HiveMQ components:

...
  # The ports can be edited or expanded upon, but the MQTT port must be the first one.
  ports:
    - name: "mqtt"
      port: 1883
      expose: true
      patch:
        - '[{"op":"add","path":"/spec/selector/hivemq.com~1node-offline","value":"false"},{"op":"add","path":"/metadata/annotations","value":{"service.spec.externalTrafficPolicy":"Local"}}]'
        # If you want Kubernetes to expose the MQTT port to external traffic
        # - '[{"op":"add","path":"/spec/type","value":"LoadBalancer"}]'
    - name: "cc"
      port: 8080
      expose: false
      patch:
        - '[{"op":"add","path":"/spec/sessionAffinity","value":"ClientIP"}]'
        # If you want Kubernetes to expose the HiveMQ control center via load balancer.
        # Warning: You should consider configuring proper security and TLS beforehand. Ingress may be a better option here.
        # - '[{"op":"add","path":"/spec/type","value":"LoadBalancer"}]'
  # To enable the HiveMQ REST API and expose it as a service. Be aware of the security risks of exposing the REST API
    - name: "api"
      port: 8888
      expose: false
      patch:
        - '[{"op":"add","path":"/spec/sessionAffinity","value":"ClientIP"}]'
...

Helm installation using custom values

For the installation using helm you have to add the official HiveMQ helm repository and install it using the modified values.yaml file.

helm repo add hivemq https://hivemq.github.io/helm-charts
helm repo update
helm upgrade --install -f values.yaml hivemq-prod hivemq/hivemq-operator # you can change "hivemq-prod" to fit your needs

Expose the HiveMQ Control Center and REST API inside the Kubernetes Cluster

The following file hivemq-service.yaml will create a Service called "hivemq-cc-service" with type ClusterIP to expose the HiveMQ Control Center and REST API inside your Kubernetes cluster.

apiVersion: v1
kind: Service
metadata:
  name: hivemq-cc-service # The service name
spec:
  ports:
  - name: "cc"
    port: 8080
    protocol: TCP
  - name: "api"
    port: 8888
    protocol: TCP
  selector:
    hivemq-cluster: hivemq-prod # from the command above

kubectl apply -f hivemq-service.yaml

NAME                                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
hivemq-cc-service                      ClusterIP   <Cluster-IP>    <none>        8080/TCP,8888/TCP   <Age>

Deploy Ingress

At this point we have already successfully deployed HiveMQ with all it’s components, but it’s only available from within the Kubernetes cluster.

To expose it outside the Kubernetes cluster, you have to set up an Kubernetes Ingress Controller as Proxy with a Ingress Resource, which will configure the Ingress Controller properly.

Keep in mind that the syntax of the following Ingress definition in ingress.yaml depends on your Kubernetes version and Ingress Controller. You can find the required informations at the documentation of your Ingress Provider.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: hivemq-ingress
  annotations:
    nginx.ingress.kubernetes.io/affinity: cookie
spec:
  rules:
  - host: <hostname> # match with your DNS setting, e.g. http://cc.hivemq.com
    http:
      paths:
      - path: / # this will match http://cc.hivemq.com/
        pathType: Exact
        backend:
          service:
            name: hivemq-cc-service # Value from hivemq-service.yaml
            port:
              number: 8080 # Value from hivemq-service.yaml
      - path: /api
        pathType: Prefix
        backend:
          service:
            name: hivemq-cc-service # Value from hivemq-service.yaml
            port:
              number: 8080 # Value from hivemq-service.yaml

kubectl apply -f ingress.yaml

This will – based on your Ingress Controller – create some resources and a Service from type LoadBalancer that will get an external IP assigned from the On-Premise or Cloud LoadBalancer, which is accessible from outside your Kubernetes Cluster.

If you have configured DNS properly, you should now be able to access your resources e.g. using http://cc.hivemq.com.

Resources

• Ingress: https://kubernetes.io/docs/concepts/services-networking/ingress/

• NGINX Ingress: https://docs.nginx.com/nginx-ingress-controller/

• Traefik Ingress: https://doc.traefik.io/traefik/providers/kubernetes-ingress/

\uD83D\uDCD8 Instructions

\uD83D\uDCCB Related articles

• Page:
  [Outdated] Running HiveMQ as a service on Windows
• Page:
  Upload file to the customer support portal
• Page:
  Override the Default logback.xml with the HiveMQ Platform Operator
• Page:
  Configuring HiveMQ Security Extension with Active Directory for MQTT Client Authentication and Authorization
• Page:
  How to access MQTT, Websocket ports using TransportServer/VirtualServer resource with nginx ingress controller