-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kubernetes #23
Comments
Hey Dimitar - we are aware and this is indeed coming shortly, thank you for the input. |
apiVersion: apps/v1
|
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:
and access the portal at 127.0.0.1:8080 with |
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
The text was updated successfully, but these errors were encountered: