CertManager Issuance failing when using 426 redirect status

[mhkarimi1383]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When using http-issuer in CertManager, since 426 is not a redirect status (and we want to use that)
Kong will respond 426 status, But We want to make it to accept http too on separately created ingress, also problem will not appear while using gateway

Expected Behavior

Since our newly created ingress is more specific

konghq.com/protocols: http

Should work

Also tried

konghq.com/regex-priority: "0"

Steps To Reproduce

1. In K8s with Kong, Install CertManager
2. Create a CertManager issuer


apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: http-issuer
spec:
  acme:
    privateKeySecretRef:
      name: http-issuer-account-key
    server: https://acme-v02.api.letsencrypt.org/directory
    solvers:
    - http01:
        ingress:
          class: kong
          ingressTemplate:
            metadata:
              annotations:
                konghq.com/protocols: http
                konghq.com/regex-priority: "0"

Kong Ingress Controller version

kong/kubernetes-ingress-controller:3.2
kong/kong-gateway:3.7-debian

Kubernetes version

Client Version: v1.31.2
Kustomize Version: v5.4.2
Server Version: v1.30.4
Kubecolor Version: 0.4.0

Anything else?

No response