[zabbix-community/zabbix] Ingress won't created

[Anton-Kartashev]

Describe the bug A clear and concise description of what the bug is.

I have set ingress.enabled=true and this error occurs. Using helm chart of ingress-nginx-4.4.3

Version of Helm and Kubernetes:

version.BuildInfo{Version:"v3.10.1", GitCommit:"9f88ccb6aee40b9a0535fcc7efea6055e1ef72c9", GitTreeState:"clean", GoVersion:"go1.18.7"}

Kubernetes v1.23.16

What happened:

Error: UPGRADE FAILED: failed to create resource: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request:

Error: exit status 1 2023/02/03 11:19:30 [warn] 301#301: the "http2_max_field_size" directive is obsolete, use the "large_client_header_buffers" directive instead in /tmp/nginx/nginx-cfg123959980:144 nginx: [warn] the "http2_max_field_size" directive is obsolete, use the "large_client_header_buffers" directive instead in /tmp/nginx/nginx-cfg123959980:144 2023/02/03 11:19:30 [warn] 301#301: the "http2_max_header_size" directive is obsolete, use the "large_client_header_buffers" directive instead in /tmp/nginx/nginx-cfg123959980:145 nginx: [warn] the "http2_max_header_size" directive is obsolete, use the "large_client_header_buffers" directive instead in /tmp/nginx/nginx-cfg123959980:145 2023/02/03 11:19:30 [warn] 301#301: the "http2_max_requests" directive is obsolete, use the "keepalive_requests" directive instead in /tmp/nginx/nginx-cfg123959980:146 nginx: [warn] the "http2_max_requests" directive is obsolete, use the "keepalive_requests" directive instead in /tmp/nginx/nginx-cfg123959980:146 2023/02/03 11:19:30 [emerg] 301#301: duplicate location "/" in /tmp/nginx/nginx-cfg123959980:574 nginx: [emerg] duplicate location "/" in /tmp/nginx/nginx-cfg123959980:574 nginx: configuration file /tmp/nginx/nginx-cfg123959980 test failed

What you expected to happen:

Create ingress route.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know:

[Anton-Kartashev]

Ingress config:

# Ingress configurations
ingress:
  # -- Enables Ingress
  enabled: true
  # -- Ingress annotations
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt
    kubernetes.io/tls-acme: "true"
    # kubernetes.io/ingress.class: nginx
  # -- Ingress hosts
  hosts:
    - host: {domain}
      paths:
        - path: /
          pathType: ImplementationSpecific
  # -- Ingress TLS configuration
  tls:
   - secretName: zabbix-tls
     hosts:
       - {domain}
  # For Kubernetes >= 1.18 you should specify the ingress-controller via the field ingressClassName
  # See https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/#specifying-the-class-of-an-ingress
  ingressClassName: nginx-zabbix
  # -- pathType is only for k8s >= 1.1=
  # pathType: Prefix

[Anton-Kartashev]

Hmm, this bug related new version of nginx ingress, downgraded to previous.