4 ms·
The orchestrator can still use cgroups for resource constraints and isolation. Or it could use virtualization - it would be an implementation detail. But devs w
by anonymous_sorry 4y ago
The orchestrator can still use cgroups for resource constraints and isolation. Or it could use virtualization - it would be an implementation detail. But devs would not have to build a container.
Binary distribution, versioning and checksumming shouldn't need to be coupled to a particular format.
Obviously docker solves a bunch of disparate problems. That's kind of the objection.
- dbxkcichhdfufu 4y agoAt that point it's not an implementation detail anymore and that's kind of the point. Static binaries are great but they don't solve every problem and they do to have to. The vast majority of usecases don't need kubernetes, that's fine too. You don't have to bash kubernetes because you don't specifically need it for your one use case. There are plenty of other perfectly valid reasons to bash that dogpile.
- anonymous_sorry 4y ago> At that point it's not an implementation detail anymore and that's kind of the point. Not clear what is meant by this. Can you elaborate? > You don't have to bash kubernetes because you don't specifically need it for your one use case. It is the platform teams at my employer deploy to, and with good reason. I think we do need it for our use case. But there are ways it could be improved, and the ability to deploy a simple Linux binary feels like one.
- dbxkcichhdfufu 4y ago