Add patch to remove root and alias directives

[rikatz]

Adds a patch to remove root and alias directives.

This directives are not required by Ingress and has been used to explore some reading of sensitive files

[k8s-ci-robot]

@rikatz: 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/test-infra repository.

[tao12345666333]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rikatz, tao12345666333

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• images/OWNERS [rikatz,tao12345666333]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[nhinze23]

Hey @rikatz,
we extend the ingress nginx image with custom pages (e.g. error page in /var/www/html) and used this root directive to point to those files.
Now this feature is a breaking change for us and we don't know a alternative way for doing such things. Can you give us a hint?
Is this maybe the complete wrong way we are doing?

With best regards

[rikatz]

Can you point me (in Slack) how you've been doing it? Iirc custom errors has its own directives @longwuyuan may know

[longwuyuan]

@nhinze23 , thanks for your update. As @rikatz said, I too feel it will help a lot to see precise details of your extensions. As suggested, you could copy/paste start a thread at https://kubernetes.slack.com in the ingress-nginx-dev channel. Thank you

[MatthewKennedy]

Trying to follow the Nginx guide for service static assets and getting this error when trying to set the root:

`-------------------------------------------------------------------------------
Error: exit status 1
2024/04/30 19:06:40 [emerg] 4403#4403: unknown directive "root" in /tmp/nginx/nginx-cfg4123983271:708
nginx: [emerg] unknown directive "root" in /tmp/nginx/nginx-cfg4123983271:708
nginx: configuration file /tmp/nginx/nginx-cfg4123983271 test failed

-------------------------------------------------------------------------------`

• https://docs.nginx.com/nginx/admin-guide/web-server/serving-static-content/
• https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/#root-inside-location-block

Can anyone point me in the right direction to add that root as suggested by Nginx?

Many thanks.

[rikatz]

We don't support root directive on ingress-nginx :) you are not supposed to serve static files from there.

Instead you should create a backend containing it, and do ingress point to that backend