Reputation: 185
Deploying Novu on Self-Hosted Kubernetes: Best Practices for Helm vs Manual Manifests
Currently running:
$ kubectl version
Client Version: v1.31.2
Kustomize Version: v5.4.2
Server Version: v1.27.2
# Self-hosted cluster
I need to deploy Novu (the open-source notification infrastructure) on my self-hosted Kubernetes cluster. I'm looking for guidance on the best approach - either using Helm charts or creating Kubernetes manifests manually.
First attempt was using kompose to convert the docker-compose file:
kompose convert -f docker-compose.yml
This didn't work well because:
No ConfigMaps were generated Missing PV/PVC configurations No Secrets management Network policies weren't properly translated Missing resource requirements and limits
I'm looking for:
A complete Helm chart configuration example textortext A set of base manifests covering:
Deployments/StatefulSets for each Novu component Required ConfigMaps PV/PVC setup Secrets management Service configurations Resource quotas and limits
This is for a production environment Need proper separation of components Must maintain scalability Requires proper persistence setup for MongoDB and Redis Need to handle environment variables securely
Any guidance or examples would be greatly appreciated!
Platform: Self-hosted Kubernetes v1.26
Infrastructure: Bare metal
Storage:
- UAT: Local storage class available
- Production: NFS server separately setup and already has a storage class
Ingress: Nginx ingress controller
Upvotes: 0
Views: 97