zabbix-community/helm-zabbix zabbix-7.0.12

on GitHub

zabbixBrowserMonitoring:
  webdriver:
    # -- Number of replicas of ``zabbixWebDriver`` module
    replicaCount: 1
    # -- set permissive podAntiAffinity to spread replicas over cluster nodes if replicaCount>1
    podAntiAffinity: true
    # -- 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:
      # -- WebDriver container image tag, See https://hub.docker.com/r/selenium/standalone-chrome/tags
      tag: 124.0-chromedriver-124.0-grid-4.33.0-20250606
    # -- WebDriver container port 1
    port1: 4444
    # -- WebDriver container port 2
    port2: 7900
  # -- Custom WebDriver URL. If set, it overrides the default internal WebDriver service URL. Set zabbixBrowserMonitoring.webdriver.enabled to false when setting this.
  customWebDriverURL: ""
  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 1 of service in Kubernetes cluster
    port1: 4444
    # -- Port 2 of service in Kubernetes cluster
    port2: 7900
    # -- NodePort port 1 to allocate on each node (only if service.type = NodePort or Loadbalancer)
    nodePort1: 31444
    # -- NodePort port 2 to allocate on each node (only if service.type = NodePort or Loadbalancer)
    nodePort2: 31900
    # -- Annotations for the Zabbix WebDriver
    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://www.selenium.dev/documentation/grid/configuration
  extraEnv: []
  #  - name: VAR_1
  #    value: 'example_value'
  # -- Annotations to add to the deployment
  extraDeploymentAnnotations: {}
  # -- Labels to add to the deployment
  extraDeploymentLabels: {}
  # -- Annotations to add to the pods
  extraPodAnnotations: {}
  # -- Labels to add to the pods
  extraPodLabels: {}
  # -- Additional volumeMounts to the Zabbix WebDriver container
  extraVolumeMounts: []
  # -- Additional containers to start within the Zabbix WebDriver pod
  extraContainers: []
  # -- Additional init containers to start within the Zabbix WebDriver pod
  extraInitContainers: []
  # -- Additional volumes to make available to the Zabbix WebDriver pod
  extraVolumes: []
  # -- Additional specifications to the Zabbix WebDriver pod
  extraPodSpecs: {}
  # -- Security Context configurations. Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
  securityContext: {}
  livenessProbe: {}
  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: {}
  # -- nodeSelector configurations. Reference: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/
  nodeSelector: {}