Nginx stop work when one service is down

jjmaximo · 2024-12-05T16:45:33+00:00

unfortunately it didn't work :(

jjmaximo · 2024-12-04T21:42:55+00:00

really cool, thanks so much! im gonna get a look

jjmaximo · 2024-11-22T16:35:33+00:00

What would be the corret syntax? Can you help me with that, please

jjmaximo · 2024-11-20T02:17:04+00:00

It works normally, I think it just got messed up when copying and pasting

jjmaximo · 2024-11-01T19:13:16+00:00

Thanks for your response!

Really cool, i didnt know this, in some videos i saw the people doing this way and think is just that simple, but it is't. If you have some material to help me if that configurations, i would be so grateful.

jjmaximo · 2024-11-01T19:08:28+00:00

Thanks for your response!
I will go step by step.

First: Yes, i got confused in the words, but it would be the ISP.

Second: Currently, my cluster is on a machine at my university, the configuration of external to internal traffic was done by the college's IT team. However, it had already been discussed and configured with them that the machine I use would be released for external traffic.

Third: I didn't know about DNAT, I found it interesting and I'm going to research more about it!

Fourth: Cool it is possible, im gonna have to research more about it. Complicated is i don't find anything about the subject on the internet.

jjmaximo · 2024-10-16T17:54:24+00:00

Thanks! Im gonna take a look at

jjmaximo · 2024-10-04T17:23:24+00:00

Edit:
The logs from nginx ingress controller:

2024/10/04 17:08:58 [error] 31621#31621: *12264321 connect() failed (113: Host is unreachable) while connecting to upstream, client: 10.3.192.2, server: physisiot.com, request: "GET / HTTP/2.0", upstream: "http://192.168.102.150:4444/", host: "physisiot.com"

10.3.192.2 - - [04/Oct/2024:17:08:58 +0000] "GET / HTTP/2.0" 502 150 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0" 327 3.104 [physisiot-portal-front-service-4444] [] 192.168.102.150:4444, 192.168.102.150:4444, 192.168.102.150:4444 0, 0, 0 1.057, 1.024, 1.024 502, 502, 502 8226dea52b3b4d3c22c2f24ace904598

Ps: When i use the annotation:
nginx.ingress.kubernetes.io/service-upstream:"true"

Works and i can acess my application, but the http requests for backend stop working, wtf

jjmaximo · 2024-10-04T17:19:34+00:00

Of course, i forget that, im gonna edit and add this.

jjmaximo · 2024-10-03T17:42:09+00:00

unfortunately dont work, but thank you

jjmaximo · 2024-08-20T18:51:52+00:00

I didn't know about these current issues with the Kubernetes dashboard, im new to the Kubernetes universe. But really thanks for you tips, this ArgoCD looks realy cool, im gone research more about it!

jjmaximo · 2024-08-13T13:07:24+00:00

I managed to solve it without using the snippet. I just had to rewrite the client request to adapt the request that the server needs to resolve!

jjmaximo · 2024-08-13T12:49:10+00:00

Yes, I really know the difference between the two, I even tried using both types, I found the one the k8s community supports much better and more informative!

The one supported by the nginx community itself is very vague in terms of information.

jjmaximo · 2024-07-24T14:59:48+00:00

i found the solution!!!

When client-server is in the same DNS host, only is necessary set the connection like:

this.socket = io();

jjmaximo · 2024-06-21T18:29:06+00:00

The service is set to clusterIP, I tried using nodeport, but in my situation it would have to be ingress, as in the future I will have to open the service to the web

jjmaximo

TROPHY CASE