Usage of configuration-snippet and server snippent issue in 4.12 version

[MichalGarnysz-TomTom]

configuration part pulled newest version

repoURL: https://kubernetes.github.io/ingress-nginx
    targetRevision: ">= 4.9.0"
    chart: ingress-nginx
    helm:
      version: v3
      values: |
        controller:
          service:
            externalTrafficPolicy: Local
            annotations:
              service.beta.kubernetes.io/azure-load-balancer-internal: "true"
              service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path: /healthz
          allowSnippetAnnotations: true

and we startet to get
"admission webhook "validate.nginx.ingress.kubernetes.io" denied the request: annotation group ServerSnippet contains risky annotation based on ingress configuration"

our services used configuration-snippet like:

     nginx.ingress.kubernetes.io/configuration-snippet: |
      more_set_headers "Access-Control-Allow-Origin: $http_origin";

[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.

[jurim76]

The issue still exists even with disabled validation webhook

I0102 13:07:55.566522       7 store.go:440] "Found valid IngressClass" ingress="tooling/keycloak" ingressclass="nginx"
E0102 13:07:55.567357       7 store.go:938] annotation group ConfigurationSnippet contains risky annotation based on ingress configuration

[Gacko]

Duplicate of #12618.