Open mitkox opened 1 year ago
Hey Dimitar - we are aware and this is indeed coming shortly, thank you for the input.
apiVersion: apps/v1 kind: Deployment metadata: name: hivemq-deployment spec: replicas: 1 selector: matchLabels: app: hivemq template: metadata: labels: app: hivemq spec: containers:
Thank you for this input - this is being tracked and we are looking to include HELM in the next revision.
Thx.
That's the one I've recently used on AKS EE for the version 2023.3:
apiVersion: apps/v1
kind: Deployment
metadata:
name: hivemqedge
spec:
replicas: 1
selector:
matchLabels:
app: hivemq-edge
template:
metadata:
labels:
app: hivemq-edge
spec:
nodeSelector:
"kubernetes.io/os": linux
containers:
- name: hivemq-edge
image: hivemq/hivemq-edge:2023.3
ports:
- containerPort: 1883
- containerPort: 8080
volumeMounts:
- name: hivemq-edge-log-volume
mountPath: /opt/hivemq/log
volumes:
- name: hivemq-edge-log-volume
emptyDir: {}
---
apiVersion: v1
kind: Service
metadata:
name: hivemq-edge
spec:
type: LoadBalancer
ports:
- port: 1883
name: hme-mqtt
- port: 8080
name: hme-ui
selector:
app: hivemq-edge
Thank you for this input, please submit your contribution via a Pull Request, such that you receive the deserved attribution. I would ask that you accept our Contribution Agreement first, and I look forward to accepting your work into the repository!
And now available as helm chart:
helm install hivemq-edge https://raw.githubusercontent.com/jmayrbaeurl/helmchart-repo/master/index/hivemq-edge-0.1.0.tgz -n hivemq-edge --create-namespace
and access the portal at 127.0.0.1:8080 with kubectl --namespace hivemq-edge port-forward $POD_NAME 8080:8080
after replacing $POD_NAME with the real pod name of hivemq-edge
Problem or use case
Can you put the helm charts or deployment yaml files for running hivemq-edge on Kubernetes? Kubernetes for edge computing is becoming the standard.
Preferred solution or suggestions