Zabbix is a mature and effortless enterprise-class open source monitoring solution for network monitoring and application monitoring of millions of metrics.

This Helm chart installs Zabbix in a Kubernetes cluster.

This helm chart is still under developpement

• Kubernetes cluster 1.10+
• Helm 3.0+
• PV provisioner support in the underlying infrastructure.

Zabbix server is the central process of Zabbix software.

The server performs the polling and trapping of data, it calculates triggers, sends notifications to users. It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems. The server can itself remotely check networked services (such as web servers and mail servers) using simple service checks.

Zabbix agent is deployed on a monitoring target to actively monitor local resources and applications (hard drives, memory, processor statistics etc).

Zabbix web interface is a part of Zabbix software. It is used to manage resources under monitoring and view monitoring statistics.

Zabbix proxy is not functional in this helm chart, yet.

Zabbix proxy is a process that may collect monitoring data from one or more monitored devices and send the information to the Zabbix server, essentially working on behalf of the server. All collected data is buffered locally and then transferred to the Zabbix server the proxy belongs to.

A database is required for zabbix to work, in this helm chart we're using Postgresql.

to use a different database make sure you use the right docker image, the docker image we're using here is for postgresql only.

The items of section Configuration can be set via --set flag during installation or change the values according to the need of the environment in helm-zabbix/values.yaml file.

• Ingress: The ingress controller must be installed in the Kubernetes cluster.
• ClusterIP: Exposes the service on a cluster-internal IP. Choosing this value makes the service only reachable from within the cluster.
• NodePort: Exposes the service on each Node’s IP at a static port (the NodePort). You’ll be able to contact the NodePort service, from outside the cluster, by requesting NodeIP:NodePort.
• LoadBalancer: Exposes the service externally using a cloud provider’s load balancer.

Install requirement kubectl and helm following the instructions this tutorial.

Access a Kubernetes cluster.

Create namespace monitoring in Kubernetes cluster.

kubectl create namespace monitoring

Add Helm repo:

helm repo add cetic https://cetic.github.io/helm-charts

Update the list helm chart available for installation (like apt-get update). This is recommend before install/upgrade a helm chart:

helm repo update

Install dependences of helm-zabbix chart:

helm dependency update

Install the Zabbix helm chart with a release name my-release in the monitoring namespace:

helm install --name my-release cetic/zabbix -n monitoring

See the example of installation in minikube in this tutorial.

See section Basic Commands of Helm 3 for more information about commands of helm.

To uninstall/delete the my-release deployment:

helm delete my-release

After deploying the chart in your cluster, you can use the following command to access the zabbix frontend service:

minikube service <release-name>-zabbix-web

The default username/password are Admin/zabbix

Apache License 2.0

The following tables lists the configurable parameters of the chart and their default values.