I have two nodes, one is control-plane node on a AWS Linux VM and other node is worker node on another AWS linux VM. I have deployed a nginx pod with container port 80 and its clusterip nginx service on port 80 (targetport: 80)

I want to send a request between two clusters using nginx on a separate server
there is an nginx server to route via upstream to two identical backends in two different clusters
, let’s say the validator application is deployed in two clusters and has different ingress addresses
validator.amd.com
validator.bm.com

I have following simple Nginx deployment in Kubernetes

I have deployed nginx in my kubernetes cluster with this configmap:

Our goal is to cache slow REST API call from kubernetes PODs to legacy CORE system. Idea is to use NGINX cache between PODs and CORE system.
Is this possible/good idea? If yes, how can we achieve this? If no what is better solution?

I’m trying to use nginx as a reverse proxy in a Kubernetes setup. We are required to verify client certificates against CRL-files, and a sidecar container is responsible for updating the CRL’s. My idea was to use “nginx -s reload” to update the configuration in the nginx-container, but for some reason the container starts a completely new master-process and since the listen-ports aren’t available it shuts down after a few seconds.
It looks like the reload is behaving correctly at first, the logs describes a graceful shutdown and starting new workers and suddenly the container is stopped.
I’ve tried the debugging version with no luck, I can’t find any root cause to the behavior.

I deployed a Kubernetes deployment with 3 pod replicas using the following yaml:

Up until now, updating the image of a pod didn’t break anything. This last time however, the pod itself got a new ip in the cluster and my service became unreachable (502 Bad Gateway). I debugged every step of the request to find the problem, from browser to container. On the logs of the ingress-nginx-controller pod, I found this suspicious line: