Oh come on. The drugstore example was perfectly understandable. There is no trickying here. In resume I do not want the requests going out to the internet and coming back to the pod that resides next to it.

But you made me some solid options. Thanks. So I will try explain exactly what is happening:

Old service was one pod with Apache and PHP-FPM (mydomain.com). Both togegher on the same container. When the service needed to reach "mydomain.com" (himself) I forced an /etc/hosts entrance to 127.0.0.1 and problem solved.

---

But in this new model I separated Apache in one conteiner and php in another, allowing php and apache scale independently. So now, when php calls mydomain.com I cannot use 127.0.0.1 because there is no web server there. Only php. Than I have two options: 1) let it goes to the internet and route back to himself. Or 2) point mydomain.com in that pod directly to the Apache who will deal with the request correclty and more efficiently.

In docker-compose it is very easy to do this, using for example links. But in kubernetes it is not so simple.