Communication between services

Question

Hello guys So the problem is that i cant access my services within cluster with HTTP requests For example i have two services `frontend and api gateway` Their ports are respectively 3000 and 3001 The main issue is that i cant do a HTTP request to http api gateway 3001 i get an `ERR NAME NOT RESOLVED` I can only do that using `external IP address http 127 10 0 7 3001 ` When i used Docker Compose i had no problems with getting access to the other services with `api gateway 3001` I am sorry in advance for it but can i ask one more question I run my own test in Garden but i cant see the `succeed` option in the Dashboard near it It uses Jest library to run the test And it really passes it Thanks in advance

damp-manchester-26851 · Answer

Some UPD I ve managed to check all the pods in Minikube but i couldnt figure out the readdressing of my services can t understand what s wrong with it

damp-manchester-26851 · Answer

UPD So i have checked all containers and tried to execute `wget` command It works great The services actually know about each other Cool But i cant make axios requests in my NodeJS application

bright-policeman-43626 · Answer

Hello < damp manchester 26851> welcome to our Discord Something that you can do to make the setup a little bit easier is use the NGINX Ingress gateway to do so simply In your localEnvironment ``` environments name local defaultNamespace $ var DEFAULT NAMESPACE variables base hostname local demo garden ``` And then in your applications you can setup the ingress like the following ``` services name api ports name http containerPort 3000 ingresses path port http hostname api $ var base hostname ``` Do this for each one of your applications and now you can do HTTP requests directly to the HTTP endpoint `api local demo garden`

bright-policeman-43626 · Answer

< damp manchester 26851> let s move the conversation here

damp-manchester-26851 · Answer

Yep

damp-manchester-26851 · Answer

So i have deleted unnecessary namespaces via `kubectl`

bright-policeman-43626 · Answer

Beautiful can you please do a `kubectl get ingress A` now to see which ingresses you have there

bright-policeman-43626 · Answer

beautiful what happens if you try to go to api local app garden in a browser

damp-manchester-26851 · Answer

It refuses the connection

bright-policeman-43626 · Answer

Ok just wanted to see Let s change baseHostname to local demo garden instead and stick with that for now

bright-policeman-43626 · Answer

Are you ok with cleaning up your namespace and deploying it again

damp-manchester-26851 · Answer

Ok i have redeployed the application

bright-policeman-43626 · Answer

you can do a `garden delete environment` this will cleanup everything including dbs and volumes

bright-policeman-43626 · Answer

and then I would get rid of the namespaces that garden manages to make sure everything gets deployed again

bright-policeman-43626 · Answer

`kubectl delete namespace garden system`

bright-policeman-43626 · Answer

also delete the nginx namespace you have there please

bright-policeman-43626 · Answer

are you db s ephemeral

damp-manchester-26851 · Answer

Oh Actually i dont know what you mean It is just only garden yml with `image mongo`

damp-manchester-26851 · Answer

So now i have sth like that

bright-policeman-43626 · Answer

oh sorry What I mean is that if your application is ok with your db getting deleted and coming back up or you have some sort of static data you didn t wanted to loose

bright-policeman-43626 · Answer

Nice so now your k8s cluster is clean Now please execute a good garden deploy and let s see what happens

damp-manchester-26851 · Answer

Huh dont mention it It is completely empty

bright-policeman-43626 · Answer

nice can you try to deploy again

damp-manchester-26851 · Answer

It is still refusing the connection

bright-policeman-43626 · Answer

Is this the case for any container or just for the API for example if you open your frontend does it work

bright-policeman-43626 · Answer

< quaint dress 831> by any chance do you have experience using Garden s ingress in Minikube < happy avocado 1035612584847622254>

damp-manchester-26851 · Answer

Nothing works

bright-policeman-43626 · Answer

sad If you do a port forward with kubernetes can you access them

bright-policeman-43626 · Answer

are you using windows or linux

damp-manchester-26851 · Answer

I use Linux Ubuntu

damp-manchester-26851 · Answer

Do you mean accessing IP like `http 127 10 0 8 8070`

bright-policeman-43626 · Answer

can you do a `kubectl get deployments A` please

bright-policeman-43626 · Answer

No port forwarding basically forwards the traffic of a K8s pod to your local

damp-manchester-26851 · Answer

Oh I have never experienced this

bright-policeman-43626 · Answer

It s alright please try this command `kubectl port forward n kaptal default deployment api gateway 3000 3001`

damp-manchester-26851 · Answer

So whats next It forwarded successfully

bright-policeman-43626 · Answer

now you can go to your browser and type localhost 3000

bright-policeman-43626 · Answer

let s see what happens

damp-manchester-26851 · Answer

Yeah i get a response from my api gateway

bright-policeman-43626 · Answer

nice so this means that your service is alright What is failing is the ingress part of the deal

damp-manchester-26851 · Answer

Its soooo weird I couldnt think that i could deal with such problem xD

bright-policeman-43626 · Answer

Well we are happy to help you in your learning experiences with Garden > Kubernetes

damp-manchester-26851 · Answer

I really appreciate that help

bright-policeman-43626 · Answer

Can you please do a `cat etc hosts` I think minikube might not be adding a Host entry to resolve DNS locally

bright-policeman-43626 · Answer

can you please add this one ``` 1 localhost ```

damp-manchester-26851 · Answer

Just to change the line under ` The following lines are desirable for IPv6 capable hosts`

bright-policeman-43626 · Answer

no don t change it

bright-policeman-43626 · Answer

add it below FarHowl entry host

bright-policeman-43626 · Answer

it has to have the same indentation

bright-policeman-43626 · Answer

yes sir beautiful

bright-policeman-43626 · Answer

can you please try again

bright-policeman-43626 · Answer

sad stuff

bright-policeman-43626 · Answer

Would you be willing to test different local kubernetes solutions

damp-manchester-26851 · Answer

I am thinking about it right now huh

bright-policeman-43626 · Answer

have you tried this one https www docker com products docker desktop

bright-policeman-43626 · Answer

I have used this one in the past and it has worked perfectly with the Ingress

damp-manchester-26851 · Answer

Let me try Is it a good soution

bright-policeman-43626 · Answer

oh yes I have had a great experience with it

bright-policeman-43626 · Answer

Please give it a try enable kubernetes and point your project to `docker desktop` context

damp-manchester-26851 · Answer

Do i need to enable Kubernetes in Docker Desktop

bright-policeman-43626 · Answer

yes after you install it

bright-policeman-43626 · Answer

you go to configuration and enable kubernetes check mark

damp-manchester-26851 · Answer

Now it works

bright-policeman-43626 · Answer

I m going to test minikube on the side as well to make sure we don t have a bug there

bright-policeman-43626 · Answer

it worked in docker desktop

damp-manchester-26851 · Answer

Yes in docker desktop

bright-policeman-43626 · Answer

can you please share your hosts again

bright-policeman-43626 · Answer

cat etc hosts

bright-policeman-43626 · Answer

yes sir Those lines added by docker desktop are the ones that makes the thing work

damp-manchester-26851 · Answer

I see

bright-policeman-43626 · Answer

I m testing minikube to make sure we don t have a bug

damp-manchester-26851 · Answer

I am interested too

damp-manchester-26851 · Answer

So am i supposed to do requests between services using ingress Why doesnt the thing as `http api gateway 3001` work

bright-policeman-43626 · Answer

can you try to just remove the port

bright-policeman-43626 · Answer

you can do either or having the ingress is just a nice feature

bright-policeman-43626 · Answer

for frontends for example

bright-policeman-43626 · Answer

oh that won t work from your browser

damp-manchester-26851 · Answer

Thats the clg from frontend function Wont it work

bright-policeman-43626 · Answer

with the ingress it will

bright-policeman-43626 · Answer

your browser is not going to be able to reach api gateway itself

damp-manchester-26851 · Answer

Ok thanks So just using ingresses

bright-policeman-43626 · Answer

correct

bright-policeman-43626 · Answer

let me know if that works

damp-manchester-26851 · Answer

Yeah that works

bright-policeman-43626 · Answer

I m glad