Michael Pleshakov

Hi @JeroenVanOort I wonder if it makes sense to deploy Ingress Controller as a daemonset in your case, via `controller.kind` paramerer. Would it solve your issue?

Thanks. We'll keep it issue open for the `strategy` related parameters.

Hi @abhisek-dwivedi > Is it possible to run IC with readOnlyRootFilesystem: true ? or some specific steps are required to do so ? We haven't tested if it's possible to...

Note about `AllowPrivilegeEscalation` To allow NGINX to bind to privileged ports like 80 and 443, we add the `NET_BIND_SERVICE` capability to the nginx binary (https://github.com/nginxinc/kubernetes-ingress/blob/master/build/Dockerfile#L267) and also allow this capability...

Hi @RichardoC I wonder if any of the following reflect your requirements? 1. *TLS termination on port 443*: the Ingress Controller terminates TLS connections on port 443, where each application...

@kbirger this restriction is intentional. While the Ingress spec allows rules with no hosts or an Ingress with no rules but with the default backend, this Ingress controller doesn't support...

@kbirger if you need to expose only one application, regardless of its DNS name, I recommend deploying NGINX without the Ingress controller, and configure NGINX using its native configuration. You...

@kbirger Yes, that is a valid case. However, what I meant by an application is that an application has a unique DNS name. This Ingress controller is designed for load...

@alvgarvilla we are not planning to support rules without hosts, as (1) this use case is not common and (2) NGINX can only handle one rule without host, because one...

@benmathews Thanks for sharing. Unfortunately, we don't have any plans to support that use case. For cases when clients don't use the DNS name, we recommend using NGINX without the...