Caution
This release has breaking changes. Back up your database and read the upgrade steps before upgrading: https://github.com/zabbix-community/helm-zabbix/tree/main/charts/zabbix#version-800
- Only Zabbix 8.0 is supported now.
- Kubernetes 1.34+ and Helm 4 are required.
- The default PostgreSQL version is now 18.
helm upgradeneedskubectl delete statefulset --cascade=orphanfirst if you usepostgresql.enabled=trueorzabbixProxy.enabled=true.
-
Bump version: chart
8.0.0, Zabbix8.0.0 -
Added support to Zabbix 8.0. Older versions of Zabbix are not supported or tested anymore.
-
Added
kubeVersion: ">=1.34.0-0"inChart.yaml. The chart is tested only with Helm 4. -
Default PostgreSQL image changed from
16to18, inpostgresql.image.tagandzabbixServer.haNodesAutoClean.image.tag. Zabbix 8.0 supports PostgreSQL 15 to 18 and TimescaleDB 2.20 to 2.29. -
New image of the HA database job (
zabbixServer.zabbixServerHA.dbCreateUpgradeJob.image.tagSuffix: "20261009150714"), built for the Zabbix 8.0 schema -
Adjusted the templates to the new compiled entrypoint of the Zabbix 8.0 images:
zabbixProxy.ZBX_SERVER_PORTis now sent inZBX_SERVER_HOSTashost:portZBX_JAVAGATEWAY_ENABLEis no longer sent to Zabbix Server or ProxyzabbixJavaGateway.ZABBIX_OPTIONSwas removed
-
Default of
zabbixProxy.ZBX_DEBUGLEVELchanged from4to3, because the Zabbix Proxy of thealpine-8.0.0image crashes with debug level 4 -
Added the headless Services
<release>-postgresql-headlessand<release>-zabbix-proxy-headless, used by the StatefulSets inserviceName -
Fixed bugs in templates:
- Zabbix Server now uses the correct Service of the Java Gateway (
<release>-java-gateway) - the Java Gateway container port is now always
10052 - the
<release>-db-accessSecret now always followspostgresAccessand keeps the password generated in the first installation, instead of generating a new one in each upgrade - the HA Labels sidecar is now deployed when HA is enabled, even with
zabbixAgent.runAsSidecar=false podAntiAffinityof Zabbix Web, Web Service, Java Gateway and WebDriver now selects the correct podsZBX_WEBDRIVERURLis now only set whenzabbixBrowserMonitoring.enabled=trueextraInitContainers,extraContainers,jobLabelsandimage.pullSecretsof the database job, andextraEnvandimage.pullSecretsofhaNodesAutoClean, now worknodePortof WebDriver and Java Gateway withLoadBalancer,namespaceof the HA RoleBinding, and the ClusterRole (extensionsreplaced bydiscovery.k8s.io)
- Zabbix Server now uses the correct Service of the Java Gateway (
-
Removed dead code: unused Ingress helpers in
_helpers.tpl, the Ingress fallback for Kubernetes < 1.18, and the orphaninit-waitschema-scriptvolume -
Added
mise.tomlto pin the versions of the tools used to develop and test the chart (helm, helm-docs, kind, kubectl, argocd) -
Improvements in
Makefile, with new targets:help,check-os,check-deps,install-deps,kind-create,deploy,undeploy,argocd-install,argocd-deploy,argocd-undeploy,stack-up,stack-down -
Added an example of deploying with Argo CD (
docs/example/argocd) and a kind cluster with 3 nodes (docs/example/kind/kind-3nodes.yaml) -
Improvements in CI:
- new
lintjob - tools installed with mise
- tests of upgrades between the Zabbix 8.0 images
- new
-
Moved
.helmignoretocharts/zabbix, so the package no longer includes docs and development files -
Adjusted the docs (
README.md,CONTRIBUTING.md,docs/requirements.md,CLAUDE.mdand therelease-chartskill) -
New helm values:
zabbixJavaGateway:
# -- Number of Java pollers started in Zabbix Server and in Zabbix Proxy to use the Java Gateway
ZBX_STARTJAVAPOLLERS: 5- Changed helm values (have break changes):
zabbixImageTag: ubuntu-8.0.0
zabbixServer:
zabbixServerHA:
dbCreateUpgradeJob:
image:
tagSuffix: "20261009150714"
haNodesAutoClean:
image:
tag: 18
postgresql:
image:
tag: 18
zabbixProxy:
ZBX_DEBUGLEVEL: 3- Removed helm values:
zabbixJavaGateway:
ZABBIX_OPTIONS: ""PRs:
Contributors: @aeciopires