News for hackers. Stuff that matters.
Re:“Let’s use Kubernetes.” Now you have eight problems by FreeHugs on Thursday March 05, 2020 @11:07AM (#22494743)

    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?
Re:“Let’s use Kubernetes.” Now you have eight problems by petilon on Thursday March 05, 2020 @12:07PM (#22495506)
What 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?
Re:“Let’s use Kubernetes.” Now you have eight problems by FreeHugs on Thursday March 05, 2020 @12:13PM (#22495587)

    What 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.
Re:“Let’s use Kubernetes.” Now you have eight problems by pmarreck on Friday March 06, 2020 @09:43AM (#22503903)
> 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

Re:“Let’s use Kubernetes.” Now you have eight problems by paulddraper on Thursday March 05, 2020 @02:28PM (#22497146)
Because you want to scale, or roll out during a deploy. Or one goes down and you need a new host.