I've been searching and looking everywhere on the internet and on these forms for days to help understand this issue and how to properly setup NGINX Ingress with Wordpress-fpm. I'm rather new to Kubernetes and all so I've been working on setting this up to help me learn it all.

I can get it to work using the image of Wordpress that has Apache included (Wordpress:latest) but I rather use NG

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.

Summary

As specified here, images on bintray should follow have an architecture appended to them:
https://github.com/Kong/kong/blob/master/CHANGELOG.md

Currently only amd64 is available.

Kong proxy does but the

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

Change the templates to run all the Tyk containers as non-root user by default, but keep an option to change the user for the gateway since there might be a legitimate use case with a host network (and privileged port).

The images should mostly work fine with this, known issues are:

• tyk-gateway container will need a pid file path configured for a non-root user accessible path
• tyk-k8s co