You can connect those two pods by using a service object.
The reason being, if the database pod goes away, it's going to come up with a different name and IP address, which means the connection string would need to be updated every time, managing that is difficult.
The service proxies traffic to pods and it also helps in load balancing of traffic if you have multiple pods to talk to.
It has its own IP and as long as service exists pod referencing this service in upstream will work and if the pods behind the service are not running, a pod will not see that and will try to forward the traffic but it will return a 502 bad gateway.
So just define the Service and then bring up your Pods with the proper label so the Service will pick them up.
Reserve a static IP and then assign ...READ MORE
The pods which are managed by ReplicationController ...READ MORE
Here is a solution to your problem:
You ...READ MORE
You can make sure that the replication ...READ MORE
Hey @nmentityvibes, you seem to be using ...READ MORE
Try using ingress itself in this manner
except ...READ MORE
Hi Kalgi after following above steps it ...READ MORE
Follow these steps:
$ kubeadm reset
$ kubeadm init ...READ MORE
Pod is a single or bunch of ...READ MORE
Make sure your imagePullPolicy is set to ...READ MORE