port-forward | simple command line utility to forward ports | Router library

Apparently, providing the DNS with format "DNS:PORT" as a parameter for AddContactPoint was not working. Using the method WithPort did the trick.

It looks like you're using the Network Policy as an ingress for incoming traffic, but what you probably want to be using is an Ingress Controller to manage Ingress traffic.

Egress is for traffic flowing outbound from your services within your cluster to external sources. Ingress is for external traffic to be directed to specific services within your cluster.

Welcome to the community!

I reproduced your example and made it work fine. I forked your repository, made some changes to js files and package.json and added Dockerfiles (you can see this commit here

Since I didn't change database settings in settings.py I attached it as a configMap to backend deployment (see here how it's done). Config map was created by this command:

kubectl create cm django1 --from-file=settings.py

The trickiest part here is to use your domain name kubernetes.docker.internal and add your port with /backend path to environment variables you're passing to your frontend application (see here)

Once this is done, it's time to set up an ingress controller (this one uses apiVersion - extestions/v1beta1 as it's done in your example, however it'll be deprecated soon, so it's advised to use networking.k8s.io/v1 - example of a newer apiVersion is here):

Totally possible. Quick test i did:

Moving this out of comments, as I was able to reproduce it on kubernetes cluster setup using kubeadm.

1 - It's pending because it doesn't have persistent volumes to proceed. Can be checked with:

kubectl get pvc output is:

If anyone comes across this problem in the future, make sure your ingress is properly configured. The error message suggests that its a misconfiguration with the ingress.

From the image you posted of the nginx-port-forward, I see you went on localhost:9443 directly, which means the Nginx server you are trying to access serve its content under /

But in the ingress definition, you define that the service will be served with path: /my-nginx. This could be the problem, as you are requesting https://example.com/my-nginx which will basically go to my-nginx:9443/my-nginx and, depending on the Pod behind this service, it could return a 404 if there's nothing at that path.

To test if the problem is what I specified above, you have a few options:

• easiest one, remove path: /my-nginx an, instead, go with path: /. You could also specify pathType: Prefix which means that everything matching the subPath specified will be served by the service.
• Add a rewrite target, which is necessary if you want to serve a service at a different path from the one expected by the application.

Add an annotation similar to the following:

What am I missing?

What you are missing is the basics of networking knowledge. Your minikube is most likely running in a VM. This VM has assigned a virtual net interface with an IP address that is known only to the mentioned linux machine it's running on and no other device in your network is aware of it, and therefore has no idea where to send the packets. Connection timeout suggests that packets get dropped somewhere (most likely on a router but firewall can also be a cause in some cases).

Try starting minikube with --driver=none, so that minikube doesn't start in a vm and gets direct access to host's network interface an its IP address.

As indicated in the question comments and in the question itself, very well documented by @vladzam, two are the reasons of the problem.

On one hand, the nginx ingress controller available through the Helm stable channel seems to be deprecated in favor of the new ingress-nginx controller - please, see the Github repo and the official documentation.

On the other, it seems to be a problem related to the definition of the Rewrite target annotation. According to the docs:

Starting in Version 0.22.0, ingress definitions using the annotation nginx.ingress.kubernetes.io/rewrite-target are not backwards compatible with previous versions. In Version 0.22.0 and beyond, any substrings within the request URI that need to be passed to the rewritten path must explicitly be defined in a capture group.

As a consequence, it is necessary to modify the definition of the ingress resource to take into account this change. For instance: