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='6.1.1'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 Configuration section 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- Removing support for non-default Kubernetes features and Custom Resource objects:
IngressRoute,Route, more info: #123 - Removing support for karpenter due to the more generalistic approach: #121
- Adding support to deploy any arbitrary manifests together with this Helm Chart by embedding them in the
.Values.extraManifestslist (#121) - From now on, the keys to use for a unifiedSecret to configure postgresql access globally for all relevant components that this Helm Chart deploys, can be configured in values.yaml
- It is now possible to use a different Schema other than "public" in Postgresql database, when using an external database
- New implementation of native Zabbix Server High Availability (see Support of native Zabbix Server High Availability section)
- No breaking changes in values.yaml, but nevertheless you might want to review your values.yaml's
zabbixServer.zabbixServerHAsection
- Will be using Postgresql 16.x and Zabbix 7.x.
- Adjust in extraEnv to add support in environment variables from configmap and secret. More info: #93
- Will be used Postgresql 15.x and Zabbix 6.x.
- Allow install zabbix-agent2 as deployment and sidecar container. More info: #20
- This release changes parameter names in preparation for addressing these issues in the future and use camelCase pattern where is possible. More info: #18 and #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 every time 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.
Since version 6.0, Zabbix has his own implementation of High Availability, which is a simple approach to realize a Hot-Standby high availability setup with Zabbix Server. This feature applies only to Zabbix Server component, not Zabbix Proxy, Webdriver, Web Frontend or such. In a Zabbix monitoring environment, by design, there can only be one central active Zabbix Server taking over the responsibility of storing data into database, calculating triggers, sending alerts, evt. The native High Availability concept does not change that, it just implements a way to have additional Zabbix Server processes being "standby" and "jumping in" as soon as the active one does not report it's availability (updating a table in the database), anymore. As such, the Zabbix Server High Availability works well together (and somewhat requires, to be an entirely high available setup), an also high available database setup. High availability of Postgres Database is not covered by this Helm Chart, but can rather easily be achieved by using one of the well-known Postgresql database operators PGO and CNPG, which are supported to be used with this Helm Chart.
For the HA feature, which has not been designed for usage in Kubernetes, to work in K8S, there have been some challenges to overcome, primarily the fact that Zabbix Server doesn't allow to upgrade or to initialize database schema when running in HA mode enabled. Intention by Zabbix is to turn HA mode off, issue Major Release Upgrade, turn HA mode back on. This doesn't conclude with Kubernetes concepts. Beside of that, some additional circumstances led us to an implementation as follows:
- added a portion in values.yaml generally switching "Zabbix Server HA" on or off. If turned off, the Zabbix Server deployment will always be started with 1 replica and without the ZBX_HANODENAME env variable. This is an easy-to-use setup with no additional job pods, but it's not possible to just scale up zabbix server pods from here
- when .Values.zabbixServer.zabbixServerHA.enabled is set to true, a Kubernetes Job, marked as Helm post-install,post-upgrade hook, is being deployed together with a Role, Rolebinding and ServiceAccount, allowing this job pod to execute some changes via Kubernetes API. The job runs after each installation and upgrade process, scales down zabbix server pods if needed, manages db entries for active HA and non-HA server nodes being connected to the database, etc. Additionally, this job figures out whether a migration from a non-HA enabled setup to a HA-enabled one has been done, and handles necessary actions (scale down pods, delete entries in database) accordingly
- the sidecar containers running together with the Zabbix Server pods have been updated not only to prevent starting Zabbix Server pods when database is not available, but also when the schema version of the database is not yet the correct one, adding an additional layer of preventing pods from crashing
Additionally, in order to make it possible to use Active checks and Active Zabbix Proxies with a Zabbix Server setup having High Availability enabled, a HA Labels sidecar has been introduced, continuously monitoring the Zabbix server pod for amount of running Zabbix server processes to figure out whether the Pod is being "active" or "standby" Zabbix Server node, and updating HA-related labels on the pod, accordingly.
The reason to implement it this way and not by probing the port number, which was my initial approach, is that probing the port of Zabbix Server will make it generate a message in the log, stating that a connection without a proper payload has been initiated towards the Zabbix Server. More info: #115
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/ |
| extraManifests | list | [] |
Extra arbitrary Kubernetes manifests to deploy within the release |
| global.commonLabels | object | {} |
Labels to apply to all resources. |
| global.imagePullSecrets | list | [] |
Reference to one or more secrets to be used when pulling images. For example: imagePullSecrets: - name: "image-pull-secret" |
| 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 |
| 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.schema | string | "" |
Schema of database. Can be left empty if unifiedSecretSchemaKey is not set. Only being used if external database is used (postgresql.enabled not set) |
| postgresAccess.unifiedSecretAutoCreate | bool | true |
automatically create secret if not already present (works only in combination with postgresql.enabled=true) |
| postgresAccess.unifiedSecretDBKey | string | "dbname" |
key of the unified postgres access secret where database name for the postgres db is found |
| postgresAccess.unifiedSecretHostKey | string | "host" |
key of the unified postgres access secret where host ip / dns name for the postgres db is found |
| postgresAccess.unifiedSecretName | string | "zabbixdb-pguser-zabbix" |
Name of one secret for unified configuration of PostgreSQL access |
| postgresAccess.unifiedSecretPasswordKey | string | "password" |
key of the unified postgres access secret where password for the postgres db is found |
| postgresAccess.unifiedSecretPortKey | string | "port" |
key of the unified postgres access secret where the port for the postgres db is found |
| postgresAccess.unifiedSecretSchemaKey | string | "" |
key of the unified postgres access secret where schema name for the postgres db is found. Can be left empty (defaults to "public", then). Only being used if external database is used (postgresql.enabled not set) |
| postgresAccess.unifiedSecretUserKey | string | "user" |
key of the unified postgres access secret where user name for the postgres db is found |
| 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.containerLabels | object | {} |
Labels 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":100} |
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 | 16 |
Tag of Docker image of Postgresql server, choice "16" for postgres "2.14.2-pg16" for timescaledb (Zabbix supports TimescaleDB 2.1.0-2.14.x. More info: https://www.zabbix.com/documentation/7.0/en/manual/installation/requirements) |
| postgresql.livenessProbe | object | {} |
The kubelet uses liveness probes to know when to restart a container. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| 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 postgres data |
| postgresql.persistence.storageSize | string | "5Gi" |
Size of the PVC to be automatically generated |
| postgresql.readinessProbe | object | {} |
The kubelet uses readiness probes to know when a container is ready to start accepting traffic. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| postgresql.resources | object | {} |
Requests and limits of pod resources. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers |
| postgresql.securityContext | object | {} |
Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ |
| postgresql.service.annotations | object | {} |
Annotations for the zabbix-server service |
| postgresql.service.clusterIP | string | nil |
clusterIP is the IP address of the service and is usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service. |
| postgresql.service.port | int | 5432 |
Port of service in Kubernetes cluster |
| postgresql.service.type | string | "ClusterIP" |
Type of service to expose the application. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. More details: https://kubernetes.io/docs/concepts/services-networking/service/ |
| postgresql.startupProbe | object | {} |
The kubelet uses startup probes to know when a container application has started. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| postgresql.statefulSetAnnotations | object | {} |
Annotations to add to the statefulset |
| postgresql.statefulSetLabels | object | {} |
Labels to add to the statefulset |
| rbac.additionalRulesForClusterRole | list | [] |
|
| rbac.create | bool | true |
Specifies whether the RBAC resources should be created |
| securityContext | object | {} |
Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ |
| serviceAccount.annotations | object | {} |
Optional additional annotations to add to the Service Account. |
| serviceAccount.automountServiceAccountToken | bool | true |
Automount API credentials for a Service Account. |
| serviceAccount.create | bool | true |
Specifies whether a service account should be created. |
| serviceAccount.labels | object | {} |
Optional additional labels to add to the Service Account. |
| serviceAccount.name | string | "" |
The name of the service account to use. If not set and create is true, a name is generated using the fullname template. |
| 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.containerLabels | object | {} |
Labels to add to the containers |
| zabbixAgent.daemonSetAnnotations | object | {} |
Annotations to add to the daemonSet |
| zabbixAgent.daemonSetLabels | object | {} |
Labels to add to the daemonSet |
| zabbixAgent.deploymentLabels | object | {} |
Labels to add to the deployment |
| 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/main/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.livenessProbe | object | {"failureThreshold":3,"periodSeconds":10,"successThreshold":1,"tcpSocket":{"port":"zabbix-agent"},"timeoutSeconds":3} |
The kubelet uses liveness probes to know when to restart a container. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| zabbixAgent.livenessProbe.tcpSocket.port | string | "zabbix-agent" |
Port number/alias name of the container |
| zabbixAgent.readinessProbe | object | {} |
The kubelet uses readiness probes to know when a container is ready to start accepting traffic. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| 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.securityContext | object | {} |
Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ |
| zabbixAgent.service.annotations | object | {} |
Annotations for the zabbix-agent service |
| zabbixAgent.service.clusterIP | string | nil |
clusterIP is the IP address of the service and is usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service. |
| zabbixAgent.service.externalIPs | list | [] |
externalIPs is a list of IP addresses for which nodes in the cluster will also accept traffic for this service. These IPs are not managed by Kubernetes. |
| zabbixAgent.service.loadBalancerClass | string | "" |
loadBalancerClass is the class of the load balancer implementation this Service belongs to. If specified, the value of this field must be a label-style identifier, with an optional prefix, e.g. "internal-vip" or "example.com/internal-vip". Unprefixed names are reserved for end-users. This field can only be set when the Service type is 'LoadBalancer'. If not set, the default load balancer implementation is used, today this is typically done through the cloud provider integration, but should apply for any default implementation. If set, it is assumed that a load balancer implementation is watching for Services with a matching class. Any default load balancer implementation (e.g. cloud providers) should ignore Services that set this field. This field can only be set when creating or updating a Service to type 'LoadBalancer'. Once set, it can not be changed. This field will be wiped when a service is updated to a non 'LoadBalancer' type. |
| zabbixAgent.service.loadBalancerIP | string | "" |
Only applies to Service Type: LoadBalancer. This feature depends on whether the underlying cloud-provider supports specifying the loadBalancerIP when a load balancer is created. This field will be ignored if the cloud-provider does not support the feature. |
| zabbixAgent.service.loadBalancerSourceRanges | list | [] |
If specified and supported by the platform, this will restrict traffic through the cloud-provider load-balancer will be restricted to the specified client IPs. This field will be ignored if the cloud-provider does not support the feature. |
| zabbixAgent.service.nodePort | int | 31050 |
NodePort port to allocate on each node (only if service.type = NodePort or Loadbalancer) |
| zabbixAgent.service.port | int | 10050 |
Port of service in Kubernetes cluster |
| zabbixAgent.service.sessionAffinity | string | "None" |
Supports "ClientIP" and "None". Used to maintain session affinity. Enable client IP based session affinity. Must be ClientIP or None. Defaults to None. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies |
| zabbixAgent.service.type | string | "ClusterIP" |
Type of service to expose the application. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. More details: https://kubernetes.io/docs/concepts/services-networking/service/ |
| zabbixAgent.startupProbe | object | {"failureThreshold":5,"initialDelaySeconds":15,"periodSeconds":5,"successThreshold":1,"tcpSocket":{"port":"zabbix-agent"},"timeoutSeconds":3} |
The kubelet uses startup probes to know when a container application has started. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| zabbixAgent.startupProbe.tcpSocket.port | string | "zabbix-agent" |
Port number/alias name of the container |
| zabbixBrowserMonitoring.customWebDriverURL | string | "" |
Custom WebDriver URL. If set, it overrides the default internal WebDriver service URL. Set zabbixBrowserMonitoring.webdriver.enabled to false when setting this. |
| zabbixBrowserMonitoring.enabled | bool | false |
Enable browser pollers |
| zabbixBrowserMonitoring.pollers | int | 1 |
Number of browser pollers to start |
| zabbixBrowserMonitoring.webdriver.enabled | bool | true |
Enable webdriver |
| zabbixBrowserMonitoring.webdriver.image.pullPolicy | string | "IfNotPresent" |
Pull policy of Docker image |
| zabbixBrowserMonitoring.webdriver.image.pullSecrets | list | [] |
List of dockerconfig secrets names to use when pulling images |
| zabbixBrowserMonitoring.webdriver.image.repository | string | "selenium/standalone-chrome" |
WebDriver container image |
| zabbixBrowserMonitoring.webdriver.image.tag | string | "127.0-chromedriver-127.0-grid-4.23.0-20240727" |
WebDriver container image tag, See https://hub.docker.com/r/selenium/standalone-chrome/tags |
| zabbixBrowserMonitoring.webdriver.name | string | "chrome" |
WebDriver container name |
| zabbixBrowserMonitoring.webdriver.port | int | 4444 |
WebDriver container port |
| zabbixImageTag | string | "ubuntu-7.0.6" |
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: 7.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 yourself. You can change version here or overwrite in each component (example: zabbixserver.image.tag, etc). |
| zabbixJavaGateway.ZBX_DEBUGLEVEL | int | 3 |
The variable is used to specify debug level, from 0 to 5 |
| zabbixJavaGateway.ZBX_JAVAGATEWAY | string | "zabbix-java-gateway" |
Additional arguments for Zabbix Java Gateway. Useful to enable additional libraries and features. ZABBIX_OPTIONS: Java Gateway Service Name |
| zabbixJavaGateway.ZBX_START_POLLERS | int | 5 |
This variable is specified amount of pollers. By default, value is 5 |
| zabbixJavaGateway.ZBX_TIMEOUT | int | 3 |
This variable is used to specify timeout for outgoing connections. By default, value is 3. |
| zabbixJavaGateway.containerAnnotations | object | {} |
Annotations to add to the containers |
| zabbixJavaGateway.containerLabels | object | {} |
Labels to add to the containers |
| zabbixJavaGateway.deploymentAnnotations | object | {} |
Annotations to add to the deployment |
| zabbixJavaGateway.deploymentLabels | object | {} |
Labels to add to the deployment |
| zabbixJavaGateway.enabled | bool | false |
Enables use of Zabbix Java Gateway |
| zabbixJavaGateway.extraContainers | list | [] |
Additional containers to start within the Zabbix Java Gateway pod |
| zabbixJavaGateway.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/main/charts/zabbix/docs/example/kind/values.yaml |
| zabbixJavaGateway.extraInitContainers | list | [] |
Additional init containers to start within the Zabbix Java Gateway pod |
| zabbixJavaGateway.extraPodSpecs | object | {} |
Additional specifications to the Zabbix Java Gateway pod |
| zabbixJavaGateway.extraVolumeMounts | list | [] |
Additional volumeMounts to the Zabbix Java Gateway container |
| zabbixJavaGateway.extraVolumes | list | [] |
Additional volumes to make available to the Zabbix Java Gateway pod |
| zabbixJavaGateway.image.pullPolicy | string | "IfNotPresent" |
Pull policy of Docker image |
| zabbixJavaGateway.image.pullSecrets | list | [] |
List of dockerconfig secrets names to use when pulling images |
| zabbixJavaGateway.image.repository | string | "zabbix/zabbix-java-gateway" |
Zabbix Java Gateway Docker image name. |
| zabbixJavaGateway.image.tag | string | nil |
Zabbix Java Gateway Docker image tag, if you want to override zabbixImageTag |
| zabbixJavaGateway.livenessProbe | object | {"failureThreshold":3,"periodSeconds":10,"successThreshold":1,"tcpSocket":{"port":"zabbix-java-gw"},"timeoutSeconds":3} |
The kubelet uses liveness probes to know when to restart a container. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| zabbixJavaGateway.livenessProbe.tcpSocket.port | string | "zabbix-java-gw" |
Port number/alias name of the container |
| zabbixJavaGateway.readinessProbe | object | {} |
The kubelet uses readiness probes to know when a container is ready to start accepting traffic. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| zabbixJavaGateway.replicaCount | int | 1 |
Number of replicas of Zabbix Java Gateway module |
| zabbixJavaGateway.resources | object | {} |
Requests and limits of pod resources. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers |
| zabbixJavaGateway.securityContext | object | {} |
Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ |
| zabbixJavaGateway.service.annotations | object | {} |
Annotations for the zabbix-java-gateway service |
| zabbixJavaGateway.service.clusterIP | string | nil |
clusterIP is the IP address of the service and is usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service. |
| zabbixJavaGateway.service.externalIPs | list | [] |
externalIPs is a list of IP addresses for which nodes in the cluster will also accept traffic for this service. These IPs are not managed by Kubernetes. |
| zabbixJavaGateway.service.loadBalancerClass | string | "" |
loadBalancerClass is the class of the load balancer implementation this Service belongs to. If specified, the value of this field must be a label-style identifier, with an optional prefix, e.g. "internal-vip" or "example.com/internal-vip". Unprefixed names are reserved for end-users. This field can only be set when the Service type is 'LoadBalancer'. If not set, the default load balancer implementation is used, today this is typically done through the cloud provider integration, but should apply for any default implementation. If set, it is assumed that a load balancer implementation is watching for Services with a matching class. Any default load balancer implementation (e.g. cloud providers) should ignore Services that set this field. This field can only be set when creating or updating a Service to type 'LoadBalancer'. Once set, it can not be changed. This field will be wiped when a service is updated to a non 'LoadBalancer' type. |
| zabbixJavaGateway.service.loadBalancerIP | string | "" |
Only applies to Service Type: LoadBalancer. This feature depends on whether the underlying cloud-provider supports specifying the loadBalancerIP when a load balancer is created. This field will be ignored if the cloud-provider does not support the feature. |
| zabbixJavaGateway.service.loadBalancerSourceRanges | list | [] |
If specified and supported by the platform, this will restrict traffic through the cloud-provider load-balancer will be restricted to the specified client IPs. This field will be ignored if the cloud-provider does not support the feature. |
| zabbixJavaGateway.service.nodePort | int | 31052 |
NodePort port to allocate on each node (only if service.type = NodePort or Loadbalancer) |
| zabbixJavaGateway.service.port | int | 10052 |
Port of service in Kubernetes cluster |
| zabbixJavaGateway.service.sessionAffinity | string | "None" |
Supports "ClientIP" and "None". Used to maintain session affinity. Enable client IP based session affinity. Must be ClientIP or None. Defaults to None. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies |
| zabbixJavaGateway.service.type | string | "ClusterIP" |
Type of service to expose the application. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. More details: https://kubernetes.io/docs/concepts/services-networking/service/ |
| zabbixJavaGateway.startupProbe | object | {"failureThreshold":5,"initialDelaySeconds":15,"periodSeconds":5,"successThreshold":1,"tcpSocket":{"port":"zabbix-java-gw"},"timeoutSeconds":3} |
The kubelet uses startup probes to know when a container application has started. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| zabbixJavaGateway.startupProbe.tcpSocket.port | string | "zabbix-java-gw" |
Port number/alias name of the container |
| 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. By 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.containerLabels | object | {} |
Labels 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/main/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.livenessProbe | object | {} |
The kubelet uses liveness probes to know when to restart a container. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| zabbixProxy.readinessProbe | object | {} |
The kubelet uses readiness probes to know when a container is ready to start accepting traffic. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| 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.securityContext | object | {} |
Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ |
| zabbixProxy.service.annotations | object | {} |
Annotations for the zabbix-proxy service |
| zabbixProxy.service.clusterIP | string | nil |
clusterIP is the IP address of the service and is usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service. |
| zabbixProxy.service.externalIPs | list | [] |
externalIPs is a list of IP addresses for which nodes in the cluster will also accept traffic for this service. These IPs are not managed by Kubernetes. |
| zabbixProxy.service.loadBalancerClass | string | "" |
loadBalancerClass is the class of the load balancer implementation this Service belongs to. If specified, the value of this field must be a label-style identifier, with an optional prefix, e.g. "internal-vip" or "example.com/internal-vip". Unprefixed names are reserved for end-users. This field can only be set when the Service type is 'LoadBalancer'. If not set, the default load balancer implementation is used, today this is typically done through the cloud provider integration, but should apply for any default implementation. If set, it is assumed that a load balancer implementation is watching for Services with a matching class. Any default load balancer implementation (e.g. cloud providers) should ignore Services that set this field. This field can only be set when creating or updating a Service to type 'LoadBalancer'. Once set, it can not be changed. This field will be wiped when a service is updated to a non 'LoadBalancer' type. |
| zabbixProxy.service.loadBalancerIP | string | "" |
Only applies to Service Type: LoadBalancer. This feature depends on whether the underlying cloud-provider supports specifying the loadBalancerIP when a load balancer is created. This field will be ignored if the cloud-provider does not support the feature. |
| zabbixProxy.service.loadBalancerSourceRanges | list | [] |
If specified and supported by the platform, this will restrict traffic through the cloud-provider load-balancer will be restricted to the specified client IPs. This field will be ignored if the cloud-provider does not support the feature. |
| zabbixProxy.service.nodePort | int | 31053 |
NodePort port to allocate on each node (only if service.type = NodePort or Loadbalancer) |
| zabbixProxy.service.port | int | 10051 |
Port of service in Kubernetes cluster |
| zabbixProxy.service.sessionAffinity | string | "None" |
Supports "ClientIP" and "None". Used to maintain session affinity. Enable client IP based session affinity. Must be ClientIP or None. Defaults to None. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies |
| zabbixProxy.service.type | string | "ClusterIP" |
Type of service to expose the application. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. More details: https://kubernetes.io/docs/concepts/services-networking/service/ |
| zabbixProxy.startupProbe | object | {} |
The kubelet uses startup probes to know when a container application has started. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| zabbixProxy.statefulSetAnnotations | object | {} |
Annotations to add to the statefulset |
| zabbixProxy.statefulSetLabels | object | {} |
Labels to add to the statefulset |
| zabbixServer.containerAnnotations | object | {} |
Annotations to add to the containers |
| zabbixServer.containerLabels | object | {} |
Labels to add to the containers |
| zabbixServer.deploymentAnnotations | object | {} |
Annotations to add to the deployment |
| zabbixServer.deploymentLabels | object | {} |
Labels 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/main/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 | {"concurrencyPolicy":"Replace","cronjobLabels":{},"deleteOlderThanSeconds":3600,"enabled":true,"extraContainers":[],"extraEnv":[],"extraInitContainers":[],"extraPodSpecs":{},"extraVolumeMounts":[],"extraVolumes":[],"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"postgres","tag":16},"resources":{},"schedule":"0 1 * * *","securityContext":{}} |
Automatically clean orphaned ha nodes from ha_nodes db table |
| zabbixServer.haNodesAutoClean.cronjobLabels | object | {} |
Labels to add to the cronjob for ha nodes autoclean |
| 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 | 16 |
Tag of Docker image of Postgresql server, choice "16" for postgres "2.14.2-pg16" for timescaledb (Zabbix supports TimescaleDB 2.1.0-2.14.x. More info: https://www.zabbix.com/documentation/7.0/en/manual/installation/requirements) |
| zabbixServer.haNodesAutoClean.resources | object | {} |
Requests and limits of pod resources. See: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers |
| zabbixServer.haNodesAutoClean.securityContext | object | {} |
Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ |
| 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.livenessProbe | object | {} |
The kubelet uses liveness probes to know when to restart a container. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| zabbixServer.podAntiAffinity | bool | true |
Set permissive podAntiAffinity to spread replicas over cluster nodes if replicaCount>1 |
| zabbixServer.readinessProbe | object | {} |
The kubelet uses readiness probes to know when a container is ready to start accepting traffic. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| 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.securityContext | object | {} |
Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ |
| zabbixServer.service.annotations | object | {} |
Annotations for the zabbix-server service |
| zabbixServer.service.clusterIP | string | nil |
clusterIP is the IP address of the service and is usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service. |
| zabbixServer.service.externalIPs | list | [] |
externalIPs is a list of IP addresses for which nodes in the cluster will also accept traffic for this service. These IPs are not managed by Kubernetes. |
| zabbixServer.service.loadBalancerClass | string | "" |
loadBalancerClass is the class of the load balancer implementation this Service belongs to. If specified, the value of this field must be a label-style identifier, with an optional prefix, e.g. "internal-vip" or "example.com/internal-vip". Unprefixed names are reserved for end-users. This field can only be set when the Service type is 'LoadBalancer'. If not set, the default load balancer implementation is used, today this is typically done through the cloud provider integration, but should apply for any default implementation. If set, it is assumed that a load balancer implementation is watching for Services with a matching class. Any default load balancer implementation (e.g. cloud providers) should ignore Services that set this field. This field can only be set when creating or updating a Service to type 'LoadBalancer'. Once set, it can not be changed. This field will be wiped when a service is updated to a non 'LoadBalancer' type. |
| zabbixServer.service.loadBalancerIP | string | "" |
Only applies to Service Type: LoadBalancer. This feature depends on whether the underlying cloud-provider supports specifying the loadBalancerIP when a load balancer is created. This field will be ignored if the cloud-provider does not support the feature. |
| zabbixServer.service.loadBalancerSourceRanges | list | [] |
If specified and supported by the platform, this will restrict traffic through the cloud-provider load-balancer will be restricted to the specified client IPs. This field will be ignored if the cloud-provider does not support the feature. |
| zabbixServer.service.nodePort | int | 31051 |
NodePort port to allocate on each node (only if service.type = NodePort or Loadbalancer) |
| zabbixServer.service.port | int | 10051 |
Port of service in Kubernetes cluster |
| zabbixServer.service.sessionAffinity | string | "None" |
Supports "ClientIP" and "None". Used to maintain session affinity. Enable client IP based session affinity. Must be ClientIP or None. Defaults to None. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies |
| zabbixServer.service.type | string | "ClusterIP" |
Type of service to expose the application. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. More details: https://kubernetes.io/docs/concepts/services-networking/service/ |
| zabbixServer.startupProbe | object | {} |
The kubelet uses startup probes to know when a container application has started. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| zabbixServer.zabbixServerHA | object | {"dbCreateUpgradeJob":{"extraContainers":[],"extraInitContainers":[],"extraPodSpecs":{},"extraVolumeMounts":[],"extraVolumes":[],"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"registry.inqbeo.de/zabbix-dev/zabbix-server-create-upgrade-db","tag":""},"resources":{},"securityContext":{}},"enabled":true,"haLabelsSidecar":{"extraVolumeMounts":[],"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"registry.inqbeo.de/zabbix-dev/zabbix-server-ha-label-manager","tag":"latest"},"labelName":"zabbix.com/server-ha-role","resources":{},"securityContext":{}},"role":{"annotations":{}},"roleBinding":{"annotations":{}},"serviceAccount":{"annotations":{}}} |
Section responsible for native Zabbix Server High Availability support of this Helm Chart |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob | object | {"extraContainers":[],"extraInitContainers":[],"extraPodSpecs":{},"extraVolumeMounts":[],"extraVolumes":[],"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"registry.inqbeo.de/zabbix-dev/zabbix-server-create-upgrade-db","tag":""},"resources":{},"securityContext":{}} |
Settings for the database initialization / upgrade job needed for HA enabled setups |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.extraContainers | list | [] |
Additional containers to start within the dbCreateUpgradeJob pod |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.extraInitContainers | list | [] |
Additional init containers to start within the dbCreateUpgradeJob pod |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.extraPodSpecs | object | {} |
Additional specifications to the dbCreateUpgradeJob pod |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.extraVolumeMounts | list | [] |
Additional volumeMounts to the dbCreateUpgradeJob pod |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.extraVolumes | list | [] |
Additional volumes to make available to the dbCreateUpgradeJob pod |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.image | object | {"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"registry.inqbeo.de/zabbix-dev/zabbix-server-create-upgrade-db","tag":""} |
Image settings for the database initialization / upgrade job |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.image.pullPolicy | string | "IfNotPresent" |
Pull policy for the db initialization / upgrade job |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.image.pullSecrets | list | [] |
Pull secrets for the db initialization / upgrade job |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.image.repository | string | "registry.inqbeo.de/zabbix-dev/zabbix-server-create-upgrade-db" |
Image repository for the database initialization / upgrade job |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.image.tag | string | "" |
it is going to be chosen based of the zabbix_server pod container otherwise |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.resources | object | {} |
Resource requests and limits for the dbCreateUpgradeJob pod |
| zabbixServer.zabbixServerHA.dbCreateUpgradeJob.securityContext | object | {} |
Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ |
| zabbixServer.zabbixServerHA.enabled | bool | true |
Enables Helm Chart support for Zabbix Server HA. If disabled, replicaCount will always be 1 |
| zabbixServer.zabbixServerHA.haLabelsSidecar | object | {"extraVolumeMounts":[],"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"registry.inqbeo.de/zabbix-dev/zabbix-server-ha-label-manager","tag":"latest"},"labelName":"zabbix.com/server-ha-role","resources":{},"securityContext":{}} |
The HA labels sidecar checks for the current pod whether it is the active Zabbix Server HA node and sets labels on it, accordingly |
| zabbixServer.zabbixServerHA.haLabelsSidecar.extraVolumeMounts | list | [] |
Extra VolumeMounts for the HA labels sidecar |
| zabbixServer.zabbixServerHA.haLabelsSidecar.image | object | {"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"registry.inqbeo.de/zabbix-dev/zabbix-server-ha-label-manager","tag":"latest"} |
Image settings for the HA labels sidecar |
| zabbixServer.zabbixServerHA.haLabelsSidecar.image.pullPolicy | string | "IfNotPresent" |
Pull policy for the HA labels sidecar image |
| zabbixServer.zabbixServerHA.haLabelsSidecar.image.pullSecrets | list | [] |
Pull secrets for the HA labels sidecar image |
| zabbixServer.zabbixServerHA.haLabelsSidecar.image.repository | string | "registry.inqbeo.de/zabbix-dev/zabbix-server-ha-label-manager" |
Repository where to get the image for the HA labels sidecar container |
| zabbixServer.zabbixServerHA.haLabelsSidecar.image.tag | string | "latest" |
Tag of the HA labels sidecar container image |
| zabbixServer.zabbixServerHA.haLabelsSidecar.labelName | string | "zabbix.com/server-ha-role" |
Label name for the sidecar to set on the zabbix server pods, will be used in the zabbix server Service as an additional selector to point to the active Zabbix Server pod |
| zabbixServer.zabbixServerHA.haLabelsSidecar.resources | object | {} |
Resource requests and limits for the HA labels sidecar |
| zabbixServer.zabbixServerHA.haLabelsSidecar.securityContext | object | {} |
Security context for the HA labels sidecar |
| zabbixServer.zabbixServerHA.role | object | {"annotations":{}} |
K8S Role being used for database initialization and upgrade job, which needs access to certain Kubernetes resources |
| zabbixServer.zabbixServerHA.role.annotations | object | {} |
Extra annotations for the role needed to give the HA related sidecars and the DB job API permissions |
| zabbixServer.zabbixServerHA.roleBinding | object | {"annotations":{}} |
Rolebinding being used for the database initialization and upgrade job |
| zabbixServer.zabbixServerHA.roleBinding.annotations | object | {} |
Extra annotations for the roleBinding needed to give the HA related DB init and upgrade job |
| zabbixServer.zabbixServerHA.serviceAccount | object | {"annotations":{}} |
Serviceaccount for the database initialization and upgrade job |
| zabbixServer.zabbixServerHA.serviceAccount.annotations | object | {} |
Extra annotations for the serviceAccount needed to give the DB job API permissions |
| zabbixWeb.containerAnnotations | object | {} |
Annotations to add to the containers |
| zabbixWeb.containerLabels | object | {} |
Labels to add to the containers |
| zabbixWeb.deploymentAnnotations | object | {} |
Annotations to add to the deployment |
| zabbixWeb.deploymentLabels | object | {} |
Labels 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/main/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 |
|
| zabbixWeb.livenessProbe.httpGet.path | string | "/" |
Path of health check of application |
| zabbixWeb.livenessProbe.httpGet.port | string | "zabbix-web" |
Port number/alias name of the container |
| zabbixWeb.livenessProbe.initialDelaySeconds | int | 30 |
|
| zabbixWeb.livenessProbe.periodSeconds | int | 10 |
|
| zabbixWeb.livenessProbe.successThreshold | int | 1 |
|
| zabbixWeb.livenessProbe.timeoutSeconds | int | 5 |
|
| zabbixWeb.podAntiAffinity | bool | true |
set permissive podAntiAffinity to spread replicas over cluster nodes if replicaCount>1 |
| zabbixWeb.readinessProbe.failureThreshold | int | 6 |
|
| zabbixWeb.readinessProbe.httpGet.path | string | "/" |
Path of health check of application |
| zabbixWeb.readinessProbe.httpGet.port | string | "zabbix-web" |
Port number/alias name of the container |
| zabbixWeb.readinessProbe.initialDelaySeconds | int | 5 |
|
| zabbixWeb.readinessProbe.periodSeconds | int | 10 |
|
| zabbixWeb.readinessProbe.successThreshold | int | 1 |
|
| zabbixWeb.readinessProbe.timeoutSeconds | int | 5 |
|
| 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.securityContext | object | {} |
Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ |
| zabbixWeb.service | object | {"annotations":{},"clusterIP":null,"externalIPs":[],"loadBalancerClass":"","loadBalancerIP":"","loadBalancerSourceRanges":[],"nodePort":31080,"port":80,"sessionAffinity":"None","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 |
clusterIP is the IP address of the service and is usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service. |
| zabbixWeb.service.externalIPs | list | [] |
externalIPs is a list of IP addresses for which nodes in the cluster will also accept traffic for this service. These IPs are not managed by Kubernetes. |
| zabbixWeb.service.loadBalancerClass | string | "" |
loadBalancerClass is the class of the load balancer implementation this Service belongs to. If specified, the value of this field must be a label-style identifier, with an optional prefix, e.g. "internal-vip" or "example.com/internal-vip". Unprefixed names are reserved for end-users. This field can only be set when the Service type is 'LoadBalancer'. If not set, the default load balancer implementation is used, today this is typically done through the cloud provider integration, but should apply for any default implementation. If set, it is assumed that a load balancer implementation is watching for Services with a matching class. Any default load balancer implementation (e.g. cloud providers) should ignore Services that set this field. This field can only be set when creating or updating a Service to type 'LoadBalancer'. Once set, it can not be changed. This field will be wiped when a service is updated to a non 'LoadBalancer' type. |
| zabbixWeb.service.loadBalancerIP | string | "" |
Only applies to Service Type: LoadBalancer. This feature depends on whether the underlying cloud-provider supports specifying the loadBalancerIP when a load balancer is created. This field will be ignored if the cloud-provider does not support the feature. |
| zabbixWeb.service.loadBalancerSourceRanges | list | [] |
If specified and supported by the platform, this will restrict traffic through the cloud-provider load-balancer will be restricted to the specified client IPs. This field will be ignored if the cloud-provider does not support the feature. |
| zabbixWeb.service.nodePort | int | 31080 |
NodePort port to allocate on each node (only if service.type = NodePort or Loadbalancer) |
| zabbixWeb.service.sessionAffinity | string | "None" |
Supports "ClientIP" and "None". Used to maintain session affinity. Enable client IP based session affinity. Must be ClientIP or None. Defaults to None. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies |
| zabbixWeb.service.type | string | "ClusterIP" |
Type of service to expose the application. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. More details: https://kubernetes.io/docs/concepts/services-networking/service/ |
| zabbixWeb.startupProbe | object | {} |
The kubelet uses startup probes to know when a container application has started. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| zabbixWebService.containerAnnotations | object | {} |
Annotations to add to the containers |
| zabbixWebService.containerLabels | object | {} |
Labels to add to the containers |
| zabbixWebService.deploymentAnnotations | object | {} |
Annotations to add to the deployment |
| zabbixWebService.deploymentLabels | object | {} |
Labels 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/main/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.livenessProbe | object | {} |
The kubelet uses liveness probes to know when to restart a container. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| zabbixWebService.podAntiAffinity | bool | true |
Set permissive podAntiAffinity to spread replicas over cluster nodes if replicaCount>1 |
| zabbixWebService.readinessProbe | object | {} |
The kubelet uses readiness probes to know when a container is ready to start accepting traffic. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
| 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.securityContext | object | {} |
Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ |
| 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 |
clusterIP is the IP address of the service and is usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service. |
| zabbixWebService.service.port | int | 10053 |
Port of service in Kubernetes cluster |
| zabbixWebService.service.type | string | "ClusterIP" |
Type of service to expose the application. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. More details: https://kubernetes.io/docs/concepts/services-networking/service/ |
| zabbixWebService.startupProbe | object | {} |
The kubelet uses startup probes to know when a container application has started. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ |
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.
- 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.