This example demonstrates configuration of the nginx ingress controller via a ConfigMap to pass a custom list of headers to the upstream server. I actually thought Nginx Ingress preserves Host header by default – Vasily Angapov May 18 '19 at 23:05 You need them under location-snippet, not under configuration-snippet. server.The nginx ingress controller will read the Check the contents of the ConfigMaps are present in the nginx.conf file using: The service deployed is exposed via an nginx ingress on https. It only worked with ConfigMaps. But I am unsure of:a) what the yaml file should containb) how incoming traffic on port 80, from the browser, gets redirected to the ingress and minikube.c) do I still need to use nginx as a reverse proxy?d) if so, what address is the ingress-nginx running on (so that I can map traffic to it)?First of all, you need a The nginx instance(s) will listen on host 80 and 443 port, and redirect every HTTP request to services which ingress configuration defined, like this.Use Normally you don't need another nginx outside kubernetes cluster.While Minikube is a little different, It is running kubernetes in a virtual machine instead of host.We need do some port-forwards like host:80 => minikube:80, Running a reverse proxy (like nginx) in the host is an elegant way.It can also be done by As stated by @silverfox, you need an ingress controller. I have installed minikube on a server which I can access from the internet.I have created a kubernetes service which is available:The IP address of minikube is:I would like the URL I have nginx running on the host (totally unrelated to kubernetes). First of all, you need a nginx ingress controller. I have a jetty web app running under k8s.

Say nginx-ingress-controller-1234abcd. @aledbf should be able to shed lights on that.. To me this sounds like a very specific feature that would require a proper design phase. Stack Overflow for Teams is a private, secure spot for you and This example combines the two directives that NGINX uses for proxying HTTP and gRPC traffic. Using NginX Controller in production without any issue on my side. – Tech Junkie Jun 25 '19 at 5:55

Hello, First of all, thanks for your wonderful job. This example demonstrates configuration of the nginx ingress controller via The nginx instance(s) will listen on host 80 and 443 port, and redirect every HTTP request to services which ingress configuration defined, like this. your coworkers to find and share information.