NGINX Ingress controller version: 0.44.0

NGINX Ingress controller Helm Chart version: 3.23.0

Kubernetes version: v1.20.2

Environment:

• Cloud provider or hardware configuration: AWS
• OS: CentOS Linux release 7.7.1908 (Core)
• Kernel: 3.10.0-1160.11.1.el7.x86_64

What happened:
when trying to deploy this chart using the following:

helm repo 

Please describe the problem you have

klogv2 has the https://godoc.org/github.com/kubernetes/klog#SetLogger API, which should let us drop the vaguely sketchy output stream we use to capture core Kubernetes log output.

NOTE: GitHub issues are reserved for bug reports only.
For anything else, please join the conversation
in Kong Nation https://discuss.konghq.com/c/kubernetes.

https://medium.com/free-code-camp/how-to-set-up-a-serious-kubernetes-terminal-dd07cab51cd4

Is there an updated ARM template that uses VMSS for nodePool creations, add them to app gateway backend pool and I would like to know how we can egress the traffic through APP Gateway as it would be the only public IP for the cluster and I still get a random IP address when I try to access a web page from a pod.

https://raw.githubusercontent.com/Azure/application-gateway-kubernetes-ingress/ma

Kubernetes v1.18 introduced a dedicated resource + field for defining IngressClass. See the documentation here: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class

It would make sense for the ingress-controller to support ingress class in this way going forward.

Related issue for skipper: zalando/skipper#1478

We can address this in our deployment yamls with this trick https://helm.sh/docs/developing_charts/#automatically-roll-deployments-when-configmaps-or-secrets-change

This will save having to helm upgrade --recreate-pods each time we want new configuration propagated to the pods.