Deploy request for nginx-kubernetes-ingress rejected.

Rejected with commit 27e662653eef3a3ce4cc88d355cd0f8235dd5cff

https://docs.netlify.com/configure-builds/environment-variables/#sensitive-variable-policy

Hi @030

Thanks for the PR! We'll look into it and get back to you shortly.

Hi @030

Most of the global configuration that affects the generated NGINX config we implement through the ConfigMap. This allows changing that configuration without re-creating the IC pods and also minimizes the number of cli args (and as a result helm chart parameters).

If this feature was implemented through the ConfigMap, I think the following ConfigMap key would be enough:

default-server-redirect-url: https://nginx.org

At the same time, another way to solve this problem could be through a more general mechanism -- server snippets. We support snippets for Ingress resources via annotations and the ConfigMap. However, we don't support them for the default server.

For example, here we configure a redirect:

default-server-server-snippets: location / { return 302 https://nginx.org; }

More use cases could be supported. Here we tell NGINX to close the connection:

default-server-server-snippets: location / { return 444; }

Here we tell NGINX to return a static response:

default-server-server-snippets: location / { return 200 "welcome from the Ingress Controller!\n"; }

The default value would be location / { return 404; }, for backward compatibilty.

I wonder what you think about the both ConfigMap approaches?

@pleshakov Thank you for the feedback. Changes have been applied and the redirect works in conjunction with a configMap as well. Could you review again?

@pleshakov Variable has been renamed and the documentation has been moved to the general customization paragraph