Michael Pleshakov

@helli0n the only method for now to change that value is to customize the template. To do that customization, it is necessary to put the whole template in the ConfigMap:...

@helli0n it appears you're using this project https://github.com/kubernetes/ingress-nginx , which is a [different](https://github.com/nginxinc/kubernetes-ingress/blob/master/docs/nginx-ingress-controllers.md) Ingress Controller. I suggest referring to its documentation.

Hi @LuciferInLove thanks for reporting! The supported regex syntax is currently limited by regular expressions supported in golang https://github.com/google/re2/wiki/Syntax We might overcome this limitation in the future. Are there any...

Ok. We'll keep the issue open to track this limitation.

Hi @danilutkin Originally we made an assumption that the ports of Ingress Controller daemonset pods would be exposed using port-mapping rather then a service, so that's why it is the...

@danilutkin not sure if that would work for you, but another approach is to patch the helm chart sources and install the IC from the patched version of the Helm...

Hi @sgasquet It should be possible to support an SSL redirect based on [`$proxy_protocol_server_port`](http://nginx.org/en/docs/http/ngx_http_core_module.html#var_proxy_protocol_server_port) variable, assuming that when NLB terminates SSL, the value is `443`, and `80` otherwise. Would it...

Hi @sgasquet Yep, the whole template needs to be applied. Unfortunately, it is not possible to modify a part of the template.

@niraj1234567890 this is not obvious, but the entire template needs to be added in the `ingress-template`, not just the excerpt.

reopening this issue, as a proper way to support this should not require a workaround, but rather a built-in feature