zabbix-5.0.2

• Updated chart version
• Updated chart documentation
• Updated Zabbix version
• Changed helm and helm-docs version
• Fix bug in volumeMount of Zabbix Agent
• Commented unnecessary helm values of example

Fixes:

• #105

PR:

• #104
• #109
• #110

Thanks @aeciopires @bonzonkim and @siegy22

zabbix-5.0.1

• Bump chart version
• Updated docs
• Updated helm version in Makefile

Fixes:

• #100

PR:

• #101

Thanks @aeciopires @mkaspar

zabbix-5.0.0

• Updated documentation
• Bump chart version
• Add to support Zabbix 7, PostgreSQL 16.x and timescaleDB 2.14.2-pg16
• Improvements in extraEnv parameter to support environment variables from configMap and Secrets #93. Thanks @Elbandi
• Updated requirements

Fixes:

• #93

PR:

• #96

Thanks @aeciopires @Elbandi

Example of using extraEnv for existing secret in Kubernetes cluster:

zabbixServer:
[...]
  extraEnv:
    - name: "ZBX_EXAMPLE_MY_ENV_1"
      value: "true"
    - name: "ZBX_EXAMPLE_MY_ENV_2"
      value: "false"
    - name: "ZBX_EXAMPLE_MY_ENV_3"
      value: "100"
    - name: MY_USERNAME
      valueFrom:
        secretKeyRef:
          name: my-envs
          key: user
    - name: MY_PASSWORD
      valueFrom:
        secretKeyRef:
          name: my-envs
          key: password
[...]          

zabbix-4.4.1

• Added new values
• Updated documentation
• Refactory in all services templates of Zabbix Components
• Bump chart version

Fixes:

• Fixed issues with exposing Zabbix components outside the Kubernetes cluster, related with the topic https://github.com/zabbix-community/helm-zabbix/discussions/27

Thanks @aeciopires

New values:

zabbixServer:
  service:
    # -- 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/
    type: ClusterIP
    # -- 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.
    clusterIP:
    # -- externalTrafficPolicy describes how nodes distribute service traffic they receive on one of the Service's "externally-facing" addresses 
    #(NodePorts, ExternalIPs, and LoadBalancer IPs). "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
    # -- 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.
    externalIPs: []
    # -- 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.
    loadBalancerIP: ""
    # -- 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.
    loadBalancerSourceRanges: []
    # -- 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.
    loadBalancerClass: ""
    # -- 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
    sessionAffinity: None
    # -- Port of service in Kubernetes cluster
    port: 10051
    # -- NodePort port to allocate on each node (only if service.type = NodePort or Loadbalancer)
    nodePort: 31051
    # -- Annotations for the zabbix-server service

postgresql:
  service:
    # -- 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/
    type: ClusterIP
    # -- 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.
    clusterIP:
    # -- Port of service in Kubernetes cluster
    port: 5432

zabbixProxy:
  service:
    # -- 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/
    type: ClusterIP
    # -- 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.
    clusterIP:
    # -- externalTrafficPolicy describes how nodes distribute service traffic they receive on one of the Service's "externally-facing" addresses 
    #(NodePorts, ExternalIPs, and LoadBalancer IPs). "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
    # -- 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.
    externalIPs: []
    # -- 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.
    loadBalancerIP: ""
    # -- 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.
    loadBalancerSourceRanges: []
    # -- 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.
    loadBalancerClass: ""
    # -- 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
    sessionAffinity: None
    # -- Port of service in Kubernetes cluster
    port: 10051
    # -- NodePort port to allocate on each node (only if service.type = NodePort or Loadbalancer)
    nodePort: 31053

zabbixAgent:
  service:
    # -- 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/
    type: ClusterIP
    # -- 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.
    clusterIP:
    # -- externalTrafficPolicy describes how nodes distribute service traffic they receive on one of the Service's "externally-facing" addresses 
    #(NodePorts, ExternalIPs, and LoadBalancer IPs). "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
    # -- 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.
    externalIPs: []
    # -- 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.
    loadBalancerIP: ""
    # -- 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.
    loadBalancerSourceRanges: []
    # -- 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 u...

zabbix-4.4.0

Fixed bugs and improvements:

• Updated documentation
• Bump chart version
• Upgraded Zabbix tag images to 6.0.30 and 6.4.15
• Added exteranlIPS and loadBalancerIP to zabbix-agent

Fixes:

• #87

PRs merged:

• #88
• #90
• #91

Thanks @aeciopires @Elbandi @szpeter80

New values:

zabbixAgent:
  # -- externalTrafficPolicy for Zabbix Agent. "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
  # -- IPs if use service type LoadBalancer"
  externalIPs: []
  loadBalancerIP: ""

zabbix-4.3.0

This release contains a small breaking change in values ​​related to the zabbixWeb component:

zabbixWeb.livenessProbe.path -> zabbixWeb.livenessProbe.httpGet.path
zabbixWeb.readinessProbe.path -> zabbixWeb.readinessProbe.httpGet.path

Fixed bugs and improvements:

• Updated documentation
• Bump chart version
• Created clusterrole and clusterrole-binding
  • Copied and adapted from: https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse/templates/
• Added installation of the Zabbix Java Gateway component (Thanks @mohammed6688)
• Added Tolerations in jobs and cronjobs (Thanks @darkxeno)
• Updated the versions of the binaries kubectl, helm and helm-docs
• Removed service of the Zabbix Agent in sidecar instalation mode
• Contents of the artifacthub-pkg.yml file updated
• Removed duplicated labels in serviceaccount and service templates
• Added custom labels and annotations to job-init-db-schema
• Created new values (see the end of this message)

Fixes:

• #23
• #79
• #81

PRs merged:

• #78
• #80

Thanks @aeciopires @mohammed6688 @darkxeno

New values:

zabbixServer:
  jobDBSchema:
    # -- Annotations to add to the jobs
    jobAnnotations: {}
    # -- Labels to add to the jobs
    jobLabels: {}
    
zabbixAgent:
  livenessProbe:
    tcpSocket:
      # -- Port number/alias name of the container
      port: zabbix-agent
    timeoutSeconds: 3
    failureThreshold: 3
    periodSeconds: 10
    successThreshold: 1
  # -- 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/
  readinessProbe: {}
  # -- 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/
  startupProbe:
    tcpSocket:
      # -- Port number/alias name of the container
      port: zabbix-agent
    initialDelaySeconds: 15
    periodSeconds: 5
    timeoutSeconds: 3
    failureThreshold: 5
    successThreshold: 1

zabbixWeb:
  livenessProbe:
    httpGet:
      # -- Path of health check of application
      path: /
      # -- Port number/alias name of the container
      port: zabbix-web
  readinessProbe:
    httpGet:
      # -- Path of health check of application
      path: /
      # -- Port number/alias name of the container
      port: zabbix-web
  # -- 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/
  startupProbe: {} 

# **Zabbix Java Gateway** configurations
zabbixJavaGateway:
  # -- Enables use of **Zabbix Java Gateway**
  enabled: false
  # -- Number of replicas of ``Zabbix Java Gateway`` module
  replicaCount: 1
  # -- Requests and limits of pod resources. See: [https://kubernetes.io/docs/concepts/configuration/manage-resources-containers](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers)
  resources: {}
  image:
    # -- Zabbix Java Gateway Docker image name.
    repository: zabbix/zabbix-java-gateway
    # -- Zabbix Java Gateway Docker image tag, if you want to override zabbixImageTag
    tag: null
    # -- Pull policy of Docker image
    pullPolicy: IfNotPresent
  ZBX_TIMEOUT: 3
  # -- Additional arguments for Zabbix Java Gateway. Useful to enable additional libraries and features.
  # ZABBIX_OPTIONS: 
  # Java Gateway Service Name
  ZBX_JAVAGATEWAY: zabbix-java-gateway
  # Java Gateway Service Port
  service:
    # -- Type of service for Zabbix Java Gateway
    type: ClusterIP
    # -- Cluster IP for Zabbix Java Gateway
    clusterIP:
    # -- Port to expose service
    port: 10052
    # -- ExternalTrafficPolicy for Zabbix Java Gateway 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
    listenOnAllInterfaces: true
    # -- NodePort port to allocate (only if service.type = NodePort)
    #nodePort: 31052
    # -- Annotations for the zabbix-java-gateway service
    annotations: {}
    # metallb.universe.tf/address-pool: production-public-ips
  # -- 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
  extraEnv: []
  # -- Additional volumeMounts to the Zabbix Java Gateway container
  extraVolumeMounts: []
  # -- Annotations to add to the deployment
  deploymentAnnotations: {}
  # -- Labels to add to the deployment
  deploymentLabels: {}
  # -- Annotations to add to the containers
  containerAnnotations: {}
  # -- Labels to add to the containers
  containerLabels: {}
  # -- Additional containers to start within the Zabbix Java Gateway pod
  extraContainers: []
  # -- Additional init containers to start within the Zabbix Java Gateway pod
  extraInitContainers: []
  # -- Additional volumes to make available to the Zabbix Java Gateway pod
  extraVolumes: []
  # -- Additional specifications to the Zabbix Java Gateway pod
  extraPodSpecs: {}
  # -- Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
  securityContext: {}
  # -- 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/
  livenessProbe:
    tcpSocket:
      # -- Port number/alias name of the container
      port: zabbix-java-gw
    timeoutSeconds: 3
    failureThreshold: 3
    periodSeconds: 10
    successThreshold: 1
  # -- 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/
  readinessProbe: {}
  # -- 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/
  startupProbe:
    tcpSocket:
      # -- Port number/alias name of the container
      port: zabbix-java-gw
    initialDelaySeconds: 15
    periodSeconds: 5
    timeoutSeconds: 3
    failureThreshold: 5
    successThreshold: 1

rbac:
  # --  Specifies whether the RBAC resources should be created
  create: true
  additionalRulesForClusterRole: []
  #  - apiGroups: [ "" ]
  #    resources:
  #      - nodes/proxy
  #    verbs: [ "get", "list", "watch" ]

zabbix-4.2.1

This version contains the follow changes:

• This version has no breaking change
• Publish new version with hotfix made by @shing6326. See #75
• Added badge with download release count
• Bumped chart version to 4.2.1
• Updated documentation of the helm chart

PRs merged:
#75
#76

Thanks @aeciopires @shing6326

zabbix-4.2.0

This version contains the follow changes:

• This version has no breaking change
• Added support to Zabbix 6.0.27 and 6.4.12
• Added optional livenessProbe, readinessProbe and startupProbe to all Zabbix components suggested by @leighwgordon in the issue #65
• Created example of readinessProbe to Zabbix-Server with two or more replicas in HA mode
• Created new optional values of livenessProbe, readinessProbe and startupProbe to all Zabbix components
• Added the ability to insert custom labels for container, deployment and statefulset. Thanks @syphernl
• Added new values ​​(see the end of this message)
• Added ServiceAccount to Zabbix components. Thanks @syphernl
• Bumped chart version to 4.2.0
• Updated documentation of the helm chart

Fixes: #70 #71

PRs merged: #69 #72 #73 #74

New values:

global:
  # -- Reference to one or more secrets to be used when pulling images.
  #
  # For example:
  #  imagePullSecrets:
  #    - name: "image-pull-secret"
  imagePullSecrets: []
  # -- Labels to apply to all resources.
  commonLabels: {}

zabbixServer:
  # -- labels to add to the deployment
  deploymentLabels: {}
  # -- labels to add to the containers
  containerLabels: {}
  # -- 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/
  livenessProbe: {}
  # -- 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/
  readinessProbe: {}
  # -- 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/
  startupProbe: {}
  
postgresql:
  # -- labels to add to the statefulset
  statefulSetLabels: {}
  # -- labels to add to the containers
  containerLabels: {}
  # -- 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/
  livenessProbe: {}
  # -- 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/
  readinessProbe: {}
  # -- 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/
  startupProbe: {}

zabbixProxy:
  # -- labels to add to the statefulset
  statefulSetLabels: {}
  # -- labels to add to the containers
  containerLabels: {}
  # -- 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/
  livenessProbe: {}
  # -- 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/
  readinessProbe: {}
  # -- 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/
  startupProbe: {}
  
zabbixAgent:
  # -- labels to add to the daemonSet
  daemonSetLabels: {}
  # -- labels to add to the deployment
  deploymentLabels: {}
  # -- labels to add to the containers
  containerLabels: {}
  # -- 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/
  livenessProbe: {}
  # -- 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/
  readinessProbe: {}
  # -- 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/
  startupProbe: {}
  
zabbixWeb:
  # -- labels to add to the deployment
  deploymentLabels: {}
  # -- labels to add to the containers
  containerLabels: {}

zabbixWebService:
  # -- labels to add to the deployment
  deploymentLabels: {}
  # -- labels to add to the containers
  containerLabels: {}
  # -- 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/
  livenessProbe: {}
  # -- 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/
  readinessProbe: {}
  # -- 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/
  startupProbe: {}

serviceAccount:
  # -- Specifies whether a service account should be created.
  create: true
  # -- The name of the service account to use. If not set and create is true, a name is generated using the fullname template.
  name: ""
  # -- Optional additional annotations to add to the Service Account.
  annotations: {}
  # -- Optional additional labels to add to the Service Account.
  labels: {}
  # -- Automount API credentials for a Service Account.
  automountServiceAccountToken: true

Thanks @aeciopires @syphernl

zabbix-4.1.0

This version contains the follow changes:

• Added support to Zabbix 6.0.26 and 6.4.11
• Added concurrencyPolicy value in cronjob
• Added new values and config to job initDBSchema
• Tested helm chart in Kubernetes 1.29.1
• Updated versions of kubectl, helm and helm-docs binaries
• Added support to Karpentes 0.33.0 in EKS 1.28
• Fixed yaml indentation
• Fixed template bug in zabbix-server template with missing imagePullPolicy
• Fixed zabbix-agent service
• Fixed initials values to PostgreSQL configmap
• Bumped chart version to 4.1.0
• Updated GH Actions and configured dependabot
• codespell: Added CI job fixing spelling issues and fix them
• This version has no breaking change
• fixes #61 #57
• PRs merged: #68 #63 #60 #59 #58 #54 #52

New values:

zabbixServer
  jobDBSchema:
    # -- additional init containers to start within the Zabbix Server Job DB Schema pod
    extraInitContainers: []
    # -- additional containers to start within the Zabbix Server Job DB Schema pod
    extraContainers: []
    # -- additional specifications to the Zabbix Server Job DB Schema pod
    extraPodSpecs: {}
    # -- additional volumeMounts to the Zabbix Server Job DB Schema pod
    extraVolumeMounts: []
    # -- additional volumes to make available to the  Zabbix Server Job DB Schema pod
    extraVolumes: []
    # -- Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
    securityContext: {}

Thanks @aeciopires @david-moreau @hebertcb @leighwgordon @mjtrangoni @tiroso

zabbix-4.0.2

This version contains the follow changes:

Fix artifacthub-pkg.yml file
Bump version
Adjust in documentation

@aeciopires