Step-by-step instructions for deploying Nightingale with Helm.
You can use the n9e helm chart to run Nightingale in a Kubernetes cluster.
The default Nightingale username is root, and the password is root.2020.
However, we do not recommend deploying Nightingale on Kubernetes, because the monitoring system is too important. If the Kubernetes cluster encounters issues, the monitoring system may stop working properly. At that point, you may want to use monitoring data to troubleshoot Kubernetes issues, creating a circular dependency. In particular, when other teams need to use the monitoring system at that moment and find it unavailable, they may come complaining to you.
FAQ
Q1: After Helm deployment the Pod keeps CrashLoopBackOff?
A:
- Check the Pod logs:
kubectl logs <pod> -n <namespace>; - Database connectivity: are MySQL / Redis reachable from inside the cluster (use Service DNS);
- ConfigMap configuration: check the db / redis addresses in
values.yaml.
Q2: Can an Operator be used instead of Helm?
A: There is no official Operator from the community at this time. Helm is the mainstream approach. If needed, you can build an Operator on top of the existing chart.
Q3: How do I upgrade the chart version?
A: helm repo update → helm upgrade n9e flashcat/n9e -f values.yaml. Back up your PVCs (persistent database directories) before upgrading.
