3 ms·
If you have microservices then you need a way for services to discover each other Why not run them in docker containers with fixed IPs?
by FreeHugs 7y ago
If you have microservices then you need
a way for services to discover each other
Why not run them in docker containers with fixed IPs?
- deleted 7y ago[deleted]
- petilon 7y agoWhat happens when the IP address changes? You need some way to lookup current IP addresses. Why re-invent DNS? Also, how do you protect these services from unauthorized access?
- FreeHugs 7y agoWhat happens when the IP address changes? Changes how? It's not as if the IP of a server magically changes out of the blue. Why re-invent DNS? There is no reason to re-invent DNS. Each docker container will have to have the info where the other containers are. So you could write that into /etc/hosts of the containers for example. Also, how do you protect these services from unauthorized access? You need to do this no matter if you use Kubernetes or your own config scripts.
- pmarreck 7y ago> What happens when the IP address changes? Erm, he literally said "with fixed IP's" (i.e. a "static IP") You DO realize this is possible and easy to configure, right? If it changes anyway after that, that's an entirely new problem. I feel like some networking knowledge will fall through the cracks eventually, static IP's might be one of those
- paulddraper 7y agoBecause you want to scale, or roll out during a deploy. Or one goes down and you need a new host.