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.
- Kubernetes cluster 1.10+
- Helm 3.0+
- Kubectl
- PV provisioner support in the underlying infrastructure (optional).
Install the kubectl and helm requirements following the instructions in this tutorial.
Attention!!! Read the Breaking changes of this helm chart.
Access the Kubernetes cluster.
Add Helm repository:
helm repo add zabbix-community https://zabbix-community.github.io/helm-zabbixUpdate the list helm charts available for installation. This is recommend prior to installation/upgrade:
helm repo updateGet all versions of helm chart:
helm search repo zabbix-community/zabbix -lSet the helm chart version you want to use. Example:
export ZABBIX_CHART_VERSION='4.0.0'Export default values of zabbix chart to $HOME/zabbix_values.yaml file:
helm show values zabbix-community/zabbix --version $ZABBIX_CHART_VERSION > $HOME/zabbix_values.yamlChange the values according to the environment in the $HOME/zabbix_values.yaml file. The items of section Configuration can be set via --set flag in
installation command or change the values according to the need of the environment in $HOME/zabbix_values.yaml file.
Test the installation/upgrade with the command:
helm upgrade --install zabbix zabbix-community/zabbix \
--dependency-update \
--create-namespace \
--version $ZABBIX_CHART_VERSION \
-f $HOME/zabbix_values.yaml -n monitoring --debug --dry-runInstall/upgrade Zabbix with the command:
helm upgrade --install zabbix zabbix-community/zabbix \
--dependency-update \
--create-namespace \
--version $ZABBIX_CHART_VERSION \
-f $HOME/zabbix_values.yaml -n monitoring --debugSee the installation example in kind cluster in this tutorial.
Create port-forward for Zabbix:
kubectl port-forward service/zabbix-zabbix-web 8888:80 -n monitoringLogin to Zabbix:
- URL: http://localhost:8888
- Login: Admin
- Password: zabbix
See the pods:
kubectl get pods -n monitoringSee details for each pod:
kubectl describe pods/POD_NAME -n monitoringSee all containers in the pod:
kubectl get pods POD_NAME -n monitoring -o jsonpath='{.spec.containers[*].name}*'See the logs for each container in the pod:
kubectl logs -f pods/POD_NAME -c CONTAINER_NAME -n monitoringAccess the container prompt.
kubectl exec -it pods/POD_NAME -c CONTAINER_NAME -n monitoring -- shSee details of Zabbix services.
kubectl get svc -n monitoring
kubectl get pods --output=wide -n monitoring
kubectl describe services zabbix -n monitoringTo uninstall/delete the zabbix deployment:
helm uninstall zabbix -n monitoring- Will be used Postgresql 15.x and Zabbix 6.x.
- Allow install zabbix-agent2 as deployment and sidecar container. More info: zabbix-community#20
- This release changes parameter names in preparation for addressing these issues in the future and use camelCase pattern where is possible. More info: zabbix-community#18 and zabbix-community#21
db_access->postgresAccessdb_access.use_unified_secret->postgresAccess.useUnifiedSecretdb_access.unified_secret_name->postgresAccess.unifiedSecretNamedb_access.unified_secret_autocreate->postgresAccess.unifiedSecretAutoCreatedb_access.db_server_host->postgresAccess.hostdb_access.db_server_port->postgresAccess.portdb_access.postgres_user->postgresAccess.userdb_access.postgres_password->postgresAccess.passworddb_access.postgres_db->postgresAccess.databasedb_access.postgres_password_secret->postgresAccess.passwordSecretdb_access.postgres_password_secret_key->postgresAccess.passwordSecretKeyingressroute->ingressRoutepostgresql.existing_claim_name->postgresql.existingClaimNamepostgresql.storage_size->postgresql.storageSizepostgresql.storage_class->postgresql.storageClasszabbix_image_tag->zabbixImageTagzabbixagent->zabbixAgentzabbixproxy->zabbixProxyzabbixserver->zabbixServerzabbixserver.pod_anti_affinity->zabbixServer.podAntiAffinityzabbixserver.ha_nodes_autoclean->zabbixServer.haNodesAutoCleanzabbixserver.ha_nodes_autoclean.delete_older_than_seconds->zabbixServer.haNodesAutoClean.deleteOlderThanSecondszabbixweb->zabbixWebzabbixweb.pod_anti_affinity->zabbixWeb.podAntiAffinityzabbixweb.saml_certs_secret_name->zabbixWeb.samlCertsSecretNamezabbixwebservice->zabbixWebServicezabbixwebservice.pod_anti_affinity->zabbixWebService.podAntiAffinityzabbixwebservice.ignore_url_cert_errors->zabbixWebService.ignoreURLCertErrors
- Will be used Postgresql 14.x and Zabbix 6.x.
- This version removes the possibility to specify database username/password per subsection in favor of specifying all of them centrally at one place.
- Also, the names of the values have changed from upper to lowercase.
- It is now possible to start the Zabbix Server pods with replicas of more than 1. HA functionality of Zabbix will automatically be enabled and it is made sure that the database schema publication will only happen once, and not by all of the Zabbix Server pods at the same time.
- More info: cetic/helm-zabbix#54
- Will be used Postgresql 14.x and Zabbix 6.x.
- This version implements a central way of managing database access credentials using a secret, which then will be respected by all the components installed by this chart: zabbixServer, zabbixWeb and postgresql.
- The secret must contain a number of keys indicating DB host, DB name, user and password and can direct towards a database installed within this chart, or an external database.
- The benefit of this is that now the database can respect the values in the central DB access secret and initialize accordingly.
- Last but not least, the credential secret can be chosen to be auto-generated (password will be set to a random string) at chart installation, if postgresql.enabled is set to true. With this, an easy to use "out-of-the-box" installation with as little customizations as possible is possible, while still obtaining a good level of security.
- More info: cetic/helm-zabbix#53
- Will be used Postgresql 14.x and Zabbix 6.x.
- The installation of any component of chart is optional for easy integration with the official chart: https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/
- More info: cetic/helm-zabbix#42
About the Zabbix version supported
- This helm chart is compatible with non-LTS version of Zabbix, that include important changes and functionalities.
- But by default this helm chart will install the latest LTS version (example: 6.0.x). See more info in Zabbix Life Cycle & Release Policy page
- When you want use a non-LTS version (example: 6.4.x), you have to set this in
values.yamlyourself.
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 Official documentation.
Zabbix Server can be operated in a High Availability mode since version 6.0 which is automatically enabled by this Helm chart when setting the Zabbix Server component to run more than 1 replica. In this HA mode, all Zabbix Server instances periodically send a heartbeat to the Database server (just updating a timestamp in a table) as well as which of the nodes is the "active" one. In case the active node does not send a heartbeat within a certain time, any of the remaining ones automatically take over. It is everytime possible to join new nodes to the HA cluster by just raising the amount of replicas of the Zabbix Server.
zabbix-agent2 is supported in this helm chart.
Zabbix Agent is deployed on a monitoring target to actively monitor local resources and applications (hard drives, memory, processor statistics etc) Official documentation.
Zabbix Web interface is a part of Zabbix software. It is used to manage resources under monitoring and view monitoring statistics Official documentation.
Zabbix Web Service is a process that is used for communication with external web services Official documentation.
This helm chart installs Zabbix Proxy with SQLite3 support
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 Official documentation.
A database is required for zabbix to work, in this helm chart we're using Postgresql.
We use plain postgresql database by default WITHOUT persistence. If you want persistence or would like to use TimescaleDB instead, check the comments in the
values.yamlfile.
About the new home of helm chart
- The new home of the Zabbix helm chart is: https://github.com/zabbix-community/helm-zabbix. It is a fork from the cetic/helm-zabbix.
- In this issue it was agreed with Sebastien Dupont that the repository would get a new home.
- We are grateful to Cetic for making the infrastructure available on CircleCI to host the helm chart from the start. Now, the new versions will be hosted on Github.
- We are very grateful to Alexandre Nuttinck and Amen Ayadi, who were the first developers of the helm chart and who worked at Cetic. Your dedication and effort made it possible to install Zabbix on a Kubernetes cluster.
The following tables lists the configurable parameters of the chart and their default values.
| Key | Type | Default | Description |
|---|---|---|---|
| affinity | object | {} |
Affinity configurations. Reference: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ |
| ingress.annotations | object | {} |
Ingress annotations |
| ingress.enabled | bool | false |
Enables Ingress |
| ingress.hosts | list | [{"host":"chart-example.local","paths":[{"path":"/","pathType":"ImplementationSpecific"}]}] |
Ingress hosts |
| ingress.pathType | string | "Prefix" |
pathType is only for k8s >= 1.1= |
| ingress.tls | list | [] |
Ingress TLS configuration |
| ingressRoute.annotations | object | {} |
IngressRoute annotations |
| ingressRoute.enabled | bool | false |
Enables Traefik IngressRoute |
| ingressRoute.entryPoints | list | ["websecure"] |
Ingressroute entrypoints |
| ingressRoute.hostName | string | "chart-example.local" |
Ingressroute host name |
| karpenter.clusterName | string | "CHANGE_HERE" |
Name of cluster. Change the term CHANGE_HERE by EKS cluster name if you want to use Karpenter. |
| karpenter.enabled | bool | false |
Enables support provisioner of Karpenter. Reference: https://karpenter.sh/. Tested only using EKS cluster 1.23 in AWS with Karpenter 0.19.2. |
| karpenter.limits | object | {"resources":{"cpu":"1000","memory":"1000Gi"}} |
Resource limits constrain the total size of the cluster. Limits prevent Karpenter from creating new instances once the limit is exceeded. |
| karpenter.tag | string | "karpenter.sh/discovery/CHANGE_HERE: CHANGE_HERE" |
Tag of discovery with name of cluster used by Karpenter. Change the term CHANGE_HERE by EKS cluster name if you want to use Karpenter. The cluster name, security group and subnets must have this tag. |
| nodeSelector | object | {} |
nodeSelector configurations. Reference: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ |
| postgresAccess.database | string | "zabbix" |
Name of database |
| postgresAccess.host | string | "zabbix-postgresql" |
Address of database host - ignored if postgresql.enabled=true |
| postgresAccess.password | string | "zabbix" |
Password of database - ignored if passwordSecret is set |
| postgresAccess.port | string | "5432" |
Port of database host - ignored if postgresql.enabled=true |
| postgresAccess.unifiedSecretAutoCreate | bool | true |
automatically create secret if not already present (works only in combination with postgresql.enabled=true) |
| postgresAccess.unifiedSecretName | string | "zabbixdb-pguser-zabbix" |
Name of one secret for unified configuration of PostgreSQL access |
| postgresAccess.useUnifiedSecret | bool | true |
Whether to use the unified PostgreSQL access secret |
| postgresAccess.user | string | "zabbix" |
User of database |
| postgresql.containerAnnotations | object | {} |
annotations to add to the containers |
| postgresql.enabled | bool | true |
Create a database using Postgresql |
| postgresql.extraContainers | list | [] |
additional containers to start within the postgresql pod |
| postgresql.extraEnv | list | [] |
Extra environment variables. A list of additional environment variables. |
| postgresql.extraInitContainers | list | [] |
additional init containers to start within the postgresql pod |
| postgresql.extraPodSpecs | object | {} |
additional specifications to the postgresql pod |
| postgresql.extraRuntimeParameters | object | {"max_connections":50} |
Extra Postgresql runtime parameters ("-c" options) |
| postgresql.extraVolumeMounts | list | [] |
additional volumeMounts to the postgresql container |
| postgresql.extraVolumes | list | [] |
additional volumes to make available to the postgresql pod |
| postgresql.image.pullPolicy | string | "IfNotPresent" |
Pull policy of Docker image |
| postgresql.image.pullSecrets | list | [] |
List of dockerconfig secrets names to use when pulling images |
| postgresql.image.repository | string | "postgres" |
Postgresql Docker image name: chose one of "postgres" or "timescale/timescaledb" |
| postgresql.image.tag | int | 15 |
Tag of Docker image of Postgresql server, choice "15" for postgres "2.11.1-pg15" for timescaledb (Zabbix supports TimescaleDB 2.0.1-2.11.x. More info: https://www.zabbix.com/documentation/6.0/en/manual/installation/requirements) Added support for PostgreSQL versions 15.x since Zabbix 6.0.10 |
| postgresql.persistence.enabled | bool | false |
whether to enable persistent storage for the postgres container or not |
| postgresql.persistence.existingClaimName | bool | false |
existing persistent volume claim name to be used to store posgres data |
| postgresql.persistence.storageSize | string | "5Gi" |
size of the PVC to be automatically generated |
| postgresql.service.annotations | object | {} |
Annotations for the zabbix-server service |
| postgresql.service.clusterIP | string | nil |
Cluster IP for Zabbix Server |
| postgresql.service.port | int | 5432 |
Port of service in Kubernetes cluster |
| postgresql.service.type | string | "ClusterIP" |
Type of service in Kubernetes cluster |
| postgresql.statefulSetAnnotations | object | {} |
annotations to add to the statefulset |
| route.annotations | object | {} |
Openshift Route extra annotations |
| route.enabled | bool | false |
Enables Route object for Openshift |
| route.hostName | string | "chart-example.local" |
Host Name for the route. Can be left empty |
| route.tls | object | {"termination":"edge"} |
Openshift Route TLS settings |
| securityContext | object | {} |
Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ |
| tolerations | list | [] |
Tolerations configurations. Reference: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/ |
| zabbixAgent.ZBX_ACTIVE_ALLOW | bool | false |
This variable is boolean (true or false) and enables or disables feature of active checks |
| zabbixAgent.ZBX_DEBUGLEVEL | int | 3 |
The variable is used to specify debug level, from 0 to 5 |
| zabbixAgent.ZBX_PASSIVE_ALLOW | bool | true |
This variable is boolean (true or false) and enables or disables feature of passive checks. By default, value is true |
| zabbixAgent.ZBX_SERVER_HOST | string | "0.0.0.0/0" |
Zabbix Server host |
| zabbixAgent.ZBX_SERVER_PORT | int | 10051 |
Zabbix Server port |
| zabbixAgent.ZBX_TIMEOUT | int | 4 |
The variable is used to specify timeout for processing checks. By default, value is 4. |
| zabbixAgent.containerAnnotations | object | {} |
annotations to add to the containers |
| zabbixAgent.daemonSetAnnotations | object | {} |
annotations to add to the daemonSet |
| zabbixAgent.enabled | bool | true |
Enables use of Zabbix Agent |
| zabbixAgent.extraContainers | list | [] |
additional containers to start within the Zabbix Agent pod |
| zabbixAgent.extraEnv | list | [] |
Extra environment variables. A list of additional environment variables. List can be extended with other environment variables listed here: https://github.com/zabbix/zabbix-docker/tree/6.0/Dockerfiles/agent2/alpine#environment-variables. See example: https://github.com/zabbix-community/helm-zabbix/blob/master/charts/zabbix/docs/example/kind/values.yaml |
| zabbixAgent.extraInitContainers | list | [] |
additional init containers to start within the Zabbix Agent pod |
| zabbixAgent.extraPodSpecs | object | {} |
additional specifications to the Zabbix Agent pod |
| zabbixAgent.extraVolumeMounts | list | [] |
additional volumeMounts to the zabbix Agent container |
| zabbixAgent.extraVolumes | list | [] |
additional volumes to make available to the Zabbix Agent pod |
| zabbixAgent.hostRootFsMount | bool | true |
If true, agent pods mounts host / at /host/root |
| zabbixAgent.image.pullPolicy | string | "IfNotPresent" |
Pull policy of Docker image |
| zabbixAgent.image.pullSecrets | list | [] |
List of dockerconfig secrets names to use when pulling images |
| zabbixAgent.image.repository | string | "zabbix/zabbix-agent2" |
Zabbix Agent Docker image name. Can use zabbix/zabbix-agent or zabbix/zabbix-agent2 |
| zabbixAgent.image.tag | string | nil |
Zabbix Agent Docker image tag, if you want to override zabbixImageTag |
| zabbixAgent.resources | object | {} |
Requests and limits of pod resources. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers |
| zabbixAgent.runAsDaemonSet | bool | false |
Enable this mode if you want to run zabbix-agent as daemonSet. The 'zabbixAgent.runAsSidecar' option must be false. |
| zabbixAgent.runAsSidecar | bool | true |
Its is a default mode. Zabbix-agent will run as sidecar in zabbix-server and zabbix-proxy pods. Disable this mode if you want to run zabbix-agent as daemonSet |
| zabbixAgent.service.annotations | object | {} |
Annotations for the zabbix-agent service |
| zabbixAgent.service.clusterIP | string | nil |
Cluster IP for Zabbix Agent |
| zabbixAgent.service.listenOnAllInterfaces | bool | true |
externalTrafficPolicy for Zabbix Agent service. "Local" to preserve sender's IP address. Please note that this might not work on multi-node clusters, depending on your network settings. externalTrafficPolicy: Local |
| zabbixAgent.service.port | int | 10050 |
Port to expose service |
| zabbixAgent.service.type | string | "ClusterIP" |
Type of service for Zabbix Agent |
| zabbixImageTag | string | "ubuntu-6.0.20" |
Zabbix components (server, agent, web frontend, ...) image tag to use. This helm chart is compatible with non-LTS version of Zabbix, that include important changes and functionalities. But by default this helm chart will install the latest LTS version (example: 6.0.x). See more info in Zabbix Life Cycle & Release Policy page When you want use a non-LTS version (example: 6.2.x), you have to set this yourself. You can change version here or overwrite in each component (example: zabbixserver.image.tag, etc). |
| zabbixProxy.ZBX_DEBUGLEVEL | int | 4 |
|
| zabbixProxy.ZBX_HOSTNAME | string | "zabbix-proxy" |
Zabbix Proxy hostname Case sensitive hostname |
| zabbixProxy.ZBX_JAVAGATEWAY_ENABLE | bool | false |
The variable enable communication with Zabbix Java Gateway to collect Java related checks. By default, value is false. |
| zabbixProxy.ZBX_PROXYMODE | int | 0 |
The variable allows to switch Zabbix Proxy mode. Bu default, value is 0 - active proxy. Allowed values are 0 and 1. |
| zabbixProxy.ZBX_SERVER_HOST | string | "zabbix-zabbix-server" |
Zabbix Server host |
| zabbixProxy.ZBX_SERVER_PORT | int | 10051 |
Zabbix Server port |
| zabbixProxy.ZBX_TIMEOUT | int | 4 |
|
| zabbixProxy.ZBX_VMWARECACHESIZE | string | "128M" |
Cache size |
| zabbixProxy.containerAnnotations | object | {} |
annotations to add to the containers |
| zabbixProxy.enabled | bool | false |
Enables use of Zabbix Proxy |
| zabbixProxy.extraContainers | list | [] |
additional containers to start within the Zabbix Proxy pod |
| zabbixProxy.extraEnv | list | [] |
Extra environment variables. A list of additional environment variables. List can be extended with other environment variables listed here: https://github.com/zabbix/zabbix-docker/tree/6.0/Dockerfiles/proxy-sqlite3/alpine#environment-variables. See example: https://github.com/zabbix-community/helm-zabbix/blob/master/charts/zabbix/docs/example/kind/values.yaml |
| zabbixProxy.extraInitContainers | list | [] |
additional init containers to start within the Zabbix Proxy pod |
| zabbixProxy.extraPodSpecs | object | {} |
additional specifications to the Zabbix Proxy pod |
| zabbixProxy.extraVolumeClaimTemplate | list | [] |
extra volumeClaimTemplate for zabbixProxy statefulset |
| zabbixProxy.extraVolumeMounts | list | [] |
additional volumeMounts to the Zabbix Proxy container |
| zabbixProxy.extraVolumes | list | [] |
additional volumes to make available to the Zabbix Proxy pod |
| zabbixProxy.image.pullPolicy | string | "IfNotPresent" |
Pull policy of Docker image |
| zabbixProxy.image.pullSecrets | list | [] |
List of dockerconfig secrets names to use when pulling images |
| zabbixProxy.image.repository | string | "zabbix/zabbix-proxy-sqlite3" |
Zabbix Proxy Docker image name |
| zabbixProxy.image.tag | string | nil |
Zabbix Proxy Docker image tag, if you want to override zabbixImageTag |
| zabbixProxy.replicaCount | int | 1 |
Number of replicas of zabbixProxy module |
| zabbixProxy.resources | object | {} |
Requests and limits of pod resources. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers |
| zabbixProxy.service.annotations | object | {} |
Annotations for the zabbix-proxy service |
| zabbixProxy.service.clusterIP | string | nil |
Cluster IP for Zabbix Proxy |
| zabbixProxy.service.port | int | 10051 |
Port to expose service |
| zabbixProxy.service.type | string | "ClusterIP" |
Type of service for Zabbix Proxy |
| zabbixProxy.statefulSetAnnotations | object | {} |
annotations to add to the statefulset |
| zabbixServer.containerAnnotations | object | {} |
annotations to add to the containers |
| zabbixServer.deploymentAnnotations | object | {} |
annotations to add to the deployment |
| zabbixServer.enabled | bool | true |
Enables use of Zabbix Server |
| zabbixServer.extraContainers | list | [] |
additional containers to start within the Zabbix Server pod |
| zabbixServer.extraEnv | list | [] |
Extra environment variables. A list of additional environment variables. List can be extended with other environment variables listed here: https://github.com/zabbix/zabbix-docker/tree/6.0/Dockerfiles/server-pgsql/alpine#environment-variables. See example: https://github.com/zabbix-community/helm-zabbix/blob/master/charts/zabbix/docs/example/kind/values.yaml |
| zabbixServer.extraInitContainers | list | [] |
additional init containers to start within the Zabbix Server pod |
| zabbixServer.extraPodSpecs | object | {} |
additional specifications to the Zabbix Server pod |
| zabbixServer.extraVolumeMounts | list | [] |
additional volumeMounts to the Zabbix Server container |
| zabbixServer.extraVolumes | list | [] |
additional volumes to make available to the Zabbix Server pod |
| zabbixServer.haNodesAutoClean | object | {"deleteOlderThanSeconds":3600,"enabled":true,"extraContainers":[],"extraEnv":[],"extraInitContainers":[],"extraPodSpecs":{},"extraVolumeMounts":[],"extraVolumes":[],"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"postgres","tag":15},"schedule":"0 1 * * *"} |
automatically clean orphaned ha nodes from ha_nodes db table |
| zabbixServer.haNodesAutoClean.extraContainers | list | [] |
additional containers to start within the cronjob hanodes autoclean |
| zabbixServer.haNodesAutoClean.extraEnv | list | [] |
Extra environment variables. A list of additional environment variables. |
| zabbixServer.haNodesAutoClean.extraInitContainers | list | [] |
additional init containers to start within the cronjob hanodes autoclean |
| zabbixServer.haNodesAutoClean.extraPodSpecs | object | {} |
additional specifications to the cronjob hanodes autoclean |
| zabbixServer.haNodesAutoClean.extraVolumeMounts | list | [] |
additional volumeMounts to the cronjob hanodes autoclean |
| zabbixServer.haNodesAutoClean.extraVolumes | list | [] |
additional volumes to make available to the cronjob hanodes autoclean |
| zabbixServer.haNodesAutoClean.image.repository | string | "postgres" |
Postgresql Docker image name: chose one of "postgres" or "timescale/timescaledb" |
| zabbixServer.haNodesAutoClean.image.tag | int | 15 |
Tag of Docker image of Postgresql server, choice "15" for postgres "2.10.3-pg15" for timescaledb (Zabbix supports TimescaleDB 2.0.1-2.10.x. More info: https://www.zabbix.com/documentation/6.0/en/manual/installation/requirements) Added support for PostgreSQL versions 15.x since Zabbix 6.0.10 |
| zabbixServer.hostIP | string | "0.0.0.0" |
optional set hostIP different from 0.0.0.0 to open port only on this IP |
| zabbixServer.hostPort | bool | false |
optional set true open a port direct on node where Zabbix Server runs |
| zabbixServer.image.pullPolicy | string | "IfNotPresent" |
Pull policy of Docker image |
| zabbixServer.image.pullSecrets | list | [] |
List of dockerconfig secrets names to use when pulling images |
| zabbixServer.image.repository | string | "zabbix/zabbix-server-pgsql" |
Zabbix Server Docker image name |
| zabbixServer.image.tag | string | nil |
Zabbix Server Docker image tag, if you want to override zabbixImageTag |
| zabbixServer.podAntiAffinity | bool | true |
set permissive podAntiAffinity to spread replicas over cluster nodes if replicaCount>1 |
| zabbixServer.replicaCount | int | 1 |
Number of replicas of zabbixServer module |
| zabbixServer.resources | object | {} |
Requests and limits of pod resources. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers |
| zabbixServer.service.annotations | object | {} |
Annotations for the zabbix-server service |
| zabbixServer.service.clusterIP | string | nil |
|
| zabbixServer.service.externalIPs | list | [] |
IPs if use service type LoadBalancer" |
| zabbixServer.service.loadBalancerIP | string | "" |
|
| zabbixServer.service.nodePort | int | 31051 |
NodePort of service on each node |
| zabbixServer.service.port | int | 10051 |
Port of service in Kubernetes cluster |
| zabbixServer.service.type | string | "ClusterIP" |
Type of service in Kubernetes cluster |
| zabbixWeb.containerAnnotations | object | {} |
annotations to add to the containers |
| zabbixWeb.deploymentAnnotations | object | {} |
annotations to add to the deployment |
| zabbixWeb.enabled | bool | true |
Enables use of Zabbix Web |
| zabbixWeb.extraContainers | list | [] |
additional containers to start within the Zabbix Web pod |
| zabbixWeb.extraEnv | list | [] |
Extra environment variables. A list of additional environment variables. List can be extended with other environment variables listed here: https://github.com/zabbix/zabbix-docker/tree/6.0/Dockerfiles/web-apache-pgsql/alpine#environment-variables. See example: https://github.com/zabbix-community/helm-zabbix/blob/master/charts/zabbix/docs/example/kind/values.yaml |
| zabbixWeb.extraInitContainers | list | [] |
additional init containers to start within the Zabbix Web pod |
| zabbixWeb.extraPodSpecs | object | {} |
additional specifications to the Zabbix Web pod |
| zabbixWeb.extraVolumeMounts | list | [] |
additional volumeMounts to the Zabbix Web container |
| zabbixWeb.extraVolumes | list | [] |
additional volumes to make available to the Zabbix Web pod |
| zabbixWeb.image.pullPolicy | string | "IfNotPresent" |
Pull policy of Docker image |
| zabbixWeb.image.pullSecrets | list | [] |
List of dockerconfig secrets names to use when pulling images |
| zabbixWeb.image.repository | string | "zabbix/zabbix-web-nginx-pgsql" |
Zabbix Web Docker image name |
| zabbixWeb.image.tag | string | nil |
Zabbix Web Docker image tag, if you want to override zabbixImageTag |
| zabbixWeb.livenessProbe.failureThreshold | int | 6 |
When a probe fails, Kubernetes will try failureThreshold times before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe the Pod will be marked Unready |
| zabbixWeb.livenessProbe.initialDelaySeconds | int | 30 |
Number of seconds after the container has started before liveness |
| zabbixWeb.livenessProbe.path | string | "/" |
Path of health check of application |
| zabbixWeb.livenessProbe.periodSeconds | int | 10 |
Specifies that the kubelet should perform a liveness probe every N seconds |
| zabbixWeb.livenessProbe.successThreshold | int | 1 |
Minimum consecutive successes for the probe to be considered successful after having failed |
| zabbixWeb.livenessProbe.timeoutSeconds | int | 5 |
Number of seconds after which the probe times out |
| zabbixWeb.podAntiAffinity | bool | true |
set permissive podAntiAffinity to spread replicas over cluster nodes if replicaCount>1 |
| zabbixWeb.readinessProbe.failureThreshold | int | 6 |
When a probe fails, Kubernetes will try failureThreshold times before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe the Pod will be marked Unready |
| zabbixWeb.readinessProbe.initialDelaySeconds | int | 5 |
Number of seconds after the container has started before readiness |
| zabbixWeb.readinessProbe.path | string | "/" |
Path of health check of application |
| zabbixWeb.readinessProbe.periodSeconds | int | 10 |
Specifies that the kubelet should perform a readiness probe every N seconds |
| zabbixWeb.readinessProbe.successThreshold | int | 1 |
Minimum consecutive successes for the probe to be considered successful after having failed |
| zabbixWeb.readinessProbe.timeoutSeconds | int | 5 |
Number of seconds after which the probe times out |
| zabbixWeb.replicaCount | int | 1 |
Number of replicas of zabbixWeb module |
| zabbixWeb.resources | object | {} |
Requests and limits of pod resources. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers |
| zabbixWeb.service | object | {"annotations":{},"clusterIP":null,"externalIPs":[],"loadBalancerIP":"","port":80,"type":"ClusterIP"} |
Certificate containing certificates for SAML configuration samlCertsSecretName: zabbix-web-samlcerts |
| zabbixWeb.service.annotations | object | {} |
Annotations for the Zabbix Web |
| zabbixWeb.service.clusterIP | string | nil |
Cluster IP for Zabbix Web |
| zabbixWeb.service.externalIPs | list | [] |
IPs if use service type LoadBalancer" |
| zabbixWeb.service.port | int | 80 |
Port to expose service |
| zabbixWeb.service.type | string | "ClusterIP" |
Type of service for Zabbix Web |
| zabbixWebService.containerAnnotations | object | {} |
annotations to add to the containers |
| zabbixWebService.deploymentAnnotations | object | {} |
annotations to add to the deployment |
| zabbixWebService.enabled | bool | true |
Enables use of Zabbix Web Service |
| zabbixWebService.extraContainers | list | [] |
additional containers to start within the Zabbix Web Service pod |
| zabbixWebService.extraEnv | list | [] |
Extra environment variables. A list of additional environment variables. List can be extended with other environment variables listed here: https://github.com/zabbix/zabbix-docker/tree/6.0/Dockerfiles/web-service/alpine#environment-variables. See example: https://github.com/zabbix-community/helm-zabbix/blob/master/charts/zabbix/docs/example/kind/values.yaml |
| zabbixWebService.extraInitContainers | list | [] |
additional init containers to start within the Zabbix Web Service pod |
| zabbixWebService.extraPodSpecs | object | {} |
additional specifications to the Zabbix Web Service pod |
| zabbixWebService.extraVolumeMounts | list | [] |
additional volumeMounts to the Zabbix Web Service container |
| zabbixWebService.extraVolumes | list | [] |
additional volumes to make available to the Zabbix Web Service pod |
| zabbixWebService.image.pullPolicy | string | "IfNotPresent" |
Pull policy of Docker image |
| zabbixWebService.image.pullSecrets | list | [] |
List of dockerconfig secrets names to use when pulling images |
| zabbixWebService.image.repository | string | "zabbix/zabbix-web-service" |
Zabbix Webservice Docker image name |
| zabbixWebService.image.tag | string | nil |
Zabbix Webservice Docker image tag, if you want to override zabbixImageTag |
| zabbixWebService.podAntiAffinity | bool | true |
set permissive podAntiAffinity to spread replicas over cluster nodes if replicaCount>1 |
| zabbixWebService.replicaCount | int | 1 |
Number of replicas of zabbixWebService module |
| zabbixWebService.resources | object | {} |
Requests and limits of pod resources. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers |
| zabbixWebService.service | object | {"annotations":{},"clusterIP":null,"port":10053,"type":"ClusterIP"} |
set the IgnoreURLCertErrors configuration setting of Zabbix Web Service ignoreURLCertErrors=1 |
| zabbixWebService.service.annotations | object | {} |
Annotations for the Zabbix Web Service |
| zabbixWebService.service.clusterIP | string | nil |
Cluster IP for Zabbix Web |
| zabbixWebService.service.port | int | 10053 |
Port to expose service |
| zabbixWebService.service.type | string | "ClusterIP" |
Type of service for Zabbix Web |
All settings referring to how the different components that this Chart installs access the
Zabbix PostgreSQL Database (either an external, already existing database or one deployed within
this Helm chart) are being configured centrally under the postgresAccess section of the
values.yaml file.
By default, this Chart will deploy it's own very simple PostgreSQL database. All settings
relevant to how to access this database will be held in one central unified secret with the
name configured with the postgresAccess.unifiedSecretName setting.
Instead of letting the Chart automatically generate such a secret with a random password
(which will NOT be recreated on upgrade/redeploy), you can supply such a secret yourself.
Use postgresAccess.unifiedSecretAutoCreate=false in such a case and read the comments
in values.yaml for how the values inside the secret should be set.
If you want to connect your Zabbix installation to a Postgres database deployed using the
CrunchyData PGO Operator,
you can use the secret that PGO generates for your DB automatically directly to connect Zabbix to it,
by just referring to its name with the postgresAccess.unifiedSecretName setting to it.
There is also the possibility to set all DB relevant settings directly inside the postgresAccess
section of the values.yaml file by using the settings noted there
(postgres_host, postgres_user, etc). If doing so, you still can use one single secret
to told just and only the database password. If you want to do so, supply the
postgresAccess.passwordSecret and postgresAccess.passwordSecretKey
settings, accordingly.
While the default database configuration shipped with this Chart is fine for most (very small,
for testing only) Zabbix installations, you will want to set some specific settings to better
match your setup. First of all, you should consider enabling Postgresql database persistence
(postgresql.persistence.enabled), as otherwise all your changes and historical data will
be gone as soon as you remove the installation of Zabbix. Additionally, you might want to tune
Postgresql by supplying extra postgresql runtime parameters using the
postgresql.extraRuntimeParameters dictionary:
postgresql:
enabled: true
persistence:
enabled: true
storageSize: 50Gi
extraRuntimeParameters:
max_connections: 250
dynamic_shared_memory_type: posix
shared_buffers: 4GB
temp_buffers: 16MB
work_mem: 128MB
maintenance_work_mem: 256MB
effective_cache_size: 6GB
min_wal_size: 80MBAlternatively, you can add your own configuration file for postgresql (using a ConfigMap and
the postgresql.extraVolumes setting) to mount it into the postgresql container and referring
to this config file with the postgresql.extraRuntimeParameters set to:
postgresql:
extraRuntimeParameters:
config.file: /path/to/your/config.file- Ingress: The ingress controller must be installed in the Kubernetes cluster.
- IngressRoute: The custom resource definition if you use the Traefik ingress controller.
- Route: The ingress controller used by Red Hat Openshift, based on HAProxy
- 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.