Kubernetes Helm

## nameOverride -- Override name of app

nameOverride: ""

## fullnameOverride -- Override the full qualified app name

fullnameOverride: ""

## kube-state-metrics.enabled -- If true, deploys the kube-state-metrics deployment

kube-state-metrics:

  enabled: true

​

## Service accoun for Kubernetes API

rbac:

  ## rbac.create  Specifies whether the RBAC resources should be created

  create: true

  additionalRulesForClusterRole: []

  ##  - apiGroups: [ "" ]

  ##    resources:

  ##      - nodes/proxy

  ##    verbs: [ "get", "list", "watch" ]

serviceAccount:

  ## serviceAccount.create  Specifies whether a service account should be created

  create: true

  ## serviceAccount.name  The name of the service account to use. If not set name is generated using the fullname template

  name: zabbix-service-account

​

​

##  **Zabbix proxy** configurations

zabbixProxy:

  ## Enables use of **Zabbix proxy**

  enabled: true

  containerSecurityContext: {}

  resources: {}

  image:

    ## Zabbix proxy Docker image name

    repository: zabbix/zabbix-proxy-sqlite3

    ## Tag of Docker image of Zabbix proxy

    tag: alpine-7.2.4

    pullPolicy: IfNotPresent

    ## List of dockerconfig secrets names to use when pulling images. Secrets must be manually created in the namespace.

    ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

    ##      https://kubernetes.io/docs/concepts/containers/images/#using-a-private-registry

    pullSecrets: []

​

  env:

    ## The variable allows to switch Zabbix proxy mode. By default, value is 0 - active proxy. Allowed values are 0 and 1.

    - name: ZBX_PROXYMODE

      value: 0

    ## Zabbix proxy hostname

    - name: ZBX_HOSTNAME

      value: zabbix-proxy

    ## Zabbix server host

    ## If ProxyMode is set to active mode:

    ## IP address or DNS name of Zabbix server to get configuration data from and send data to.

​

    ## If ProxyMode is set to passive mode:

    ## List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix server. Incoming connections will be accepted only from the addresses listed here. If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.

    ## Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com

​

    ## Note that since version 6.0 the variable ZBX_SERVER_PORT is not supported anymore. Instead, add a colon (:) followed by the port number to the end of ZBX_SERVER_HOST value.

    - name: ZBX_SERVER_HOST

      value: "127.0.0.1"

    ## The variable is used to specify debug level. By default, value is 3

    - name: ZBX_DEBUGLEVEL

      value: 3

    ## Cache size

    - name: ZBX_CACHESIZE

      value: 128M

    # This variable is specified amount of pre-forked instances of Java pollers. By default, value is 5 when zabbixJavaGateway enable.

    # - name: ZBX_STARTJAVAPOLLERS

    #   value: 0

    ## How often the proxy retrieves configuration data from Zabbix server in seconds. Active proxy parameter. Ignored for passive proxies.

    - name: ZBX_PROXYCONFIGFREQUENCY

      value: 10

    ## List can be extended with other environment variables listed here: https://github.com/zabbix/zabbix-docker/tree/trunk/Dockerfiles/proxy-sqlite3#other-variables

    ## For example:

    ## The variable is list of comma separated loadable Zabbix modules.

    ## - name: ZBX_LOADMODULE

    ##   value : dummy1.so,dummy2.so

​

  ## The startupProbe, livenessProbe, readinessProbe variables

  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

​

  livenessProbe:

    tcpSocket:

      port: zabbix-proxy

    timeoutSeconds: 3

    failureThreshold: 3

    periodSeconds: 10

    successThreshold: 1

​

  readinessProbe: {}

​

  startupProbe: