Lua scripts in controller 1.12.0 Doesnt work

[FaraSys]

What happened:
Hello everyone.

Last week, I updated the Ingress controllers from version 1.11.2 to 1.12.0, and I started experiencing issues when using Lua scripts through the configuration-snippet annotation.

I created an Ingress resource (you can see the YAML below) that includes the configuration-snippet annotation referencing my Lua script. After applying this Ingress resource, when I try to access it, I receive a 404 HTTP response.

Next, I logged into the Ingress controller and opened the nginx.conf file, and noticed that the server block for my resource is simply missing.

If I remove the configuration-snippet annotation, the resource appears in the nginx.conf configuration file of the controller.

Could you please help me resolve this issue?

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: qpba-mid
  namespace: mid
  annotations:
    ingress.kubernetes.io/ssl-redirect: 'true'
    ingress.kubernetes.io/use-port-in-redirects: 'true'
    nginx.ingress.kubernetes.io/enable-cors: 'true'
    nginx.ingress.kubernetes.io/force-ssl-redirect: 'true'
    nginx.ingress.kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/proxy-buffering: 'off'
    nginx.ingress.kubernetes.io/proxy-max-temp-file-size: 256m
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/server-snippet: |
      access_by_lua_file /etc/nginx/lua/qpba.lua;
spec:
  ingressClassName: nginx
  tls:
    - hosts:
        - qpba-mid.domain.net
      secretName: tls-cert
  rules:
    - host: qpba-mid.domain.net
      http:
        paths:
          - path: /mid(/|$)(.*)
            pathType: Prefix
            backend:
              service:
                name: mid
                port:
                  number: 80

What you expected to happen:

1. Successfully parse and include the Lua script in the NGINX configuration.

2. Create the corresponding server block in the nginx.conf file.

3. Allow access to the resource without any issues, returning the appropriate HTTP response (e.g., 200 OK) when accessed.

In other words, the Ingress resource should work as intended, with the Lua script being executed as part of the NGINX configuration, and the resource should be accessible without errors.

NGINX Ingress controller version (exec into the pod and run /nginx-ingress-controller --version):
NGINX Ingress controller
Release: v1.12.0
Build: ba73b2c
Repository:
https://github.com/kubernetes/ingress-nginx
nginx version: nginx/1.25.5

Kubernetes version (use kubectl version):
Client Version: v1.30.8
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.8
Environment:

• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
  PRETTY_NAME="Ubuntu 22.04.5 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04.5 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/"
  SUPPORT_URL="https://help.ubuntu.com/"
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
  UBUNTU_CODENAME=jammy
• Kernel (e.g. uname -a):
  Linux node-01 5.15.0-134-generic fix wrong links and punctuations #145-Ubuntu SMP Wed Feb 12 20:08:39 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
• Install tools:
  • Please mention how/where was the cluster created like kubeadm/kops/minikube/kind etc.
    kubead
• Basic cluster related info:
  • kubectl version Client Version: v1.30.8

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Gacko]

Snippet annotations are of annotation risk level Critical and therefore disabled by default in v1.12.0. You need to raise your annotation risk level back to Critical to enable them: #11819