v3.1.3

• The new home of the Zabbix helm chart is: https://github.com/zabbix-community/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.

v3.1.2

This version contains the follow changes:

• Added support to extraVolumeClaimTemplate for pod of Zabbix Proxy;
• Bumped chart version;
• Changed Zabbix version installed by default.

More info:
#73

Thanks @tomsozolins for your review and contribution.

v3.1.1

This version allow:

• Hotfix about initContainers;
• Bump chart version;
• Added notice about Zabbix version installed by default;
• Change Zabbix version installed by default.

More info:
#70

Thanks @sa-ChristianAnton for your review and contribution.

v3.1.0

This version allow:

• To install Zabbix 6.2 as default;
• To add extra specifications for pods of zabbix components;
• To create init containers;
• To verify apiversion available of Cronjobs.

More info:
#65
#66
#67
#69

Thanks @tomsozolins @david-moreau and @maxenced for your contribution.

v3.0.1

• This version allow specify different versions between components of Zabbix, if necessary. By default will be used version unique specified in parameter zabbix_image_tag. See issue #62
• Bump Zabbix version in Chart.yaml file;
• Added comments of some parameters;
• Adjust in documentation;
• Adjust in example values;
• Added file of reviewers.

Thanks @scoopex for your contribution.

v3.0.0

Break change 3.0.0

• 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.
• See README.md file for more instruction

This version solve issues #38, #58 and #60.

Thanks @sa-ChristianAnton for one month of effort and great work with the helm chart. Welcome to mainteners list.

v2.0.1

Hotfix of issue #55

Thanks @acritelli

v2.0.0

Break change 2.0.0

• Will be used Postgresql 14.x and Zabbix 6.0.4.
• 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: #53

Thanks @sa-ChristianAnton

v1.2.0

This version allows users to configure a secret for connecting to postgresql server, instead of using clear text strings.

Configurable for both server and web.

Thanks @plicon

v1.1.0

Add optional annotations for zabbix-service, zabbix-proxy, zabbix-agent and zabbix-web. Can be used for requesting a specific ip-pool from metallb.

Thanks @plicon