News for hackers. Stuff that matters.
Re:“Let’s use Kubernetes.” Now you have eight problems by Legogris on Thursday March 05, 2020 @11:11AM (#22494784)
Portability - the idea being that you can migrate to an orchestration technology that makes sense when you have the need. The cost and effort of containerizing any single service from the get-go should be minimal. It also helps a lot with reproducibility, local testing, tests in CI, etc.

Valid reasons to not run containerized in production can be specific security restrictions or performance requirements. I could line up several things that are not suitable for containers, but if you're in a position of "simple but growing web app that doesn't really warrant kubernetes right now" (the comment I was replying to), I think it's good rule of thumb.

I agree with your main argument, of course.

Re:“Let’s use Kubernetes.” Now you have eight problems by geggam on Thursday March 05, 2020 @12:10PM (#22495543)
The overhead managing a container ecosystem to run production is not trivial. IF you are doing this in a service then by all means leverage that package methodology.

If you are managing your systems who already have a robust package management layer then adding the container stacks on top of managing the OS layers you have just doubled the systems your operations team is managing.

Containers also bring NAT and all sorts of DNS / DHCP issues that require extremely senior well rounded guys to manage.

Developers dont see this complexity and think containers are great.

Effectively containers moves the complexity of managing source code into infrastructure where you have to manage that complexity.

The tools to manage source code are mature. The tools to manage complex infrastructure are not mature and the people with the skills required to do so ... are rare.

Re:“Let’s use Kubernetes.” Now you have eight problems by Legogris on Thursday March 05, 2020 @12:24PM (#22495703)
> If you are managing your systems who already have a robust package management layer then adding the container stacks on top of managing the OS layers you have just doubled the systems your operations team is managing.

Oh yeah, if you're not building the software in-house it's a lot less clear that "Containerizate Everything!" is the answer every time. Though there are stable helm charts for a lot of the commonly used software out there, do whatever works for you, man ;)

> Containers also bring NAT and all sorts of DNS / DHCP issues that require extremely senior well rounded guys to manage.

I mean, at that point you can just run with host mode networking and it's all the same, no?

Re:“Let’s use Kubernetes.” Now you have eight problems by scarface74 on Thursday March 05, 2020 @02:31PM (#22497173)
Or you can just use ECS/Fargate and each container registers itself to Route53 and you can just use DNS...
Re:“Let’s use Kubernetes.” Now you have eight problems by scarface74 on Thursday March 05, 2020 @02:26PM (#22497119)
Out of all of the business concerns that a startup or basically any company has, “cloud lock in” is at the bottom of the list.