3 ms·
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 methodo
by geggam 7y ago
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.
- Legogris 7y ago> 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?
- scarface74 7y agoOr you can just use ECS/Fargate and each container registers itself to Route53 and you can just use DNS...