The ingress-nginx controller crashes due to `unknown directive "alias"` when using global snippets. about ingress-nginx

[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/test-infra repository.

[longwuyuan]

/remove-kind bug
/kind support

Try the root directive https://nginx.org/en/docs/http/ngx_http_core_module.html#alias

The nginx directives you choose are not coded in the controller, just to state the obvious.

Please feel free to re-open the issue and add the details as asked in a new bug report template, in case you find problem in the controller itself.

/close

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to this:

/remove-kind bug
/kind support

Try the root directive https://nginx.org/en/docs/http/ngx_http_core_module.html#alias

The nginx directives you choose are not coded in the controller, just to state the obvious.

Please feel free to re-open the issue and add the details as asked in a new bug report template, in case you find problem in the controller itself.

/close

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.

[longwuyuan]

Actually I was wrong earlier (or maybe not as you are using snippet.sorry not clear) It seems the project removed the support for both alias and root directive #8624

Example of a custom backend service with custom error pages https://kubernetes.github.io/ingress-nginx/examples/customization/custom-errors/

[albgus]

Ok, that is a bit unfortunate. As mentioned in my original issue the documented method doesn't work because it enforces overwriting all errors returned from the backend, which is not what I want. However perhaps it's possible to implement something similar to the included error handling with a custom backend.