garden version: 0.13.8 rust: 1.70 node:18.16.0-alpine running Linux dev 5.10.102.1-microsoft-standard-WSL2 --- Sorry for the n00b question but I'm at my wit's end. I have a rust backend with a node frontend, both copies of examples from the examples directory from Garden's github. The only thing different is that I've changed the routes so that they should correspond. Here is the repo: https://github.com/matthewaerose/test-of-rust-with-frontend I can reach the backend through its ingress I can reach the frontend through its ingress But when it comes time for the frontend to contact the backend, I get

{
  "error": {
    "cause": {
      "errno": -111,
      "code": "ECONNREFUSED",
      "syscall": "connect",
      "address": "127.0.0.1",
      "port": 80
    }
  },
  "message": "Unable to reach service at http://backend.rust.local.demo.garden"
}

--- I check the svc with

kubectl get svc

and see it doesn't have an ExternalIP.

NAME       TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
backend    ClusterIP   10.105.208.217   <none>        80/TCP     21m
frontend   ClusterIP   10.97.105.9      <none>        8080/TCP   16m

--- I execute a curl from ingress pod to backend and it returns

kephalos@dev:~/test-of-rust-with-frontend$ k exec -n garden-system garden-nginx-ingress-nginx-controller-j9gff -- curl -X GET backend.rust.local.demo.garden
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    17  100    17    0     0     55      0 --:--:-- --:--:-- --:--:--    55Hello, Rust 🦀!

Please let me know if there is any additional info I could provide that could be helpful. Thank you!

Hi @few-magazine-85406 thanks for asking Kapa before opening a post and welcome to our community 👋 . I'm taking a look at this now.

@few-magazine-85406 Thank you for providing the repo. I just tried it out and the reason you are running into

ECONNREFUSED

error is because the backend URL that you have specified in frontend/app.js is not correct. please change

const backendServiceEndpoint = `http://backend.rust.local.demo.garden`

with

const backendServiceEndpoint = `http://backend/`

Basically, you do not need to specify the ingress URL there but rather use the service url as it's service-to-service communication between the frontend & backend services inside your namespace. Please give it a try and let us know if it still doesn't work.

@astonishing-tomato-18259 @quaint-dress-831 thank you for the responses! I've tried out your suggestion and it works! But I don't understand why. My understanding was that the browser was the one making the call and wouldn't have any idea of

http://backend

. I've even removed the ingress from the backend.garden.yaml and it still works, thinking maybe there was some "behind the scenes magic" happening. I thought the flow would be

browser->DNS->loadBalancer->service

. How is the browser able to hit the service directly?

If you look at the code: https://github.com/matthewaerose/test-of-rust-with-frontend/blob/master/frontend/app.js#L10 frontend is basically a node/express service that simply exposes 2 endpoints

/hello-frontend

and

/call-backend

. So browser isn't responsible for calling the backend here but rather the frontend node/express service is responsible for calling the backend. The name frontend migth be a bit confusing here but in fact the backend & frontend in /demo-project are 2 nodejs services.