4 ms·
The discussion here is not the method of deployment, but the infra architecture. You don't need k8s, containers, and multiple cloud instances to automate deplo
by rmbyrro 3y ago
The discussion here is not the method of deployment, but the infra architecture.
You don't need k8s, containers, and multiple cloud instances to automate deployment.
It's perfectly possible and simple to implement a button to deploy on a single machine.
Heck, on OVH or Hetzner, you can have a dedicated bare metal machine with many cores and RAM exclusive to you, cheaper than famous cloud instances. These bare metals will handle what takes sometimes hundreds of containers to handle, with a much simple and easy to maintain infra.
- moondev 3y agoYou can deploy k8s on a single machine though. This way you get the benefit of a standardized, documented API without the burden of multiple machines.
- zer00eyz 3y agoYour still setting up K8's... I have scp'd my go binary and set it up in system d. Nothing about K8 or containers are light... they are buckets where bad devs hide the bodies in most cases.
- moondev 3y agokubernetes is also a static go binary (kubelet) deployed with systemd!
- hparadiz 3y agoWhy use k8s over just a docker container?
- zer00eyz 3y agoDont deploy docker in production. Podman. You could but why all the extra overhead?
- hparadiz 3y agoDocker has no overhead on the Linux kernel. It just runs things for you via LXC. The overhead is no different from any other process.
- zer00eyz 3y agoThe last time I checked docker was libcontainer and not running lxc any longer. Libcontaier lxc all use the same api calls to the kernel... so in effect your still correct (mostly) They all have overhead, if you're starting to use their features... cgroups can have some very funny impacts on app performance more so if your running containers ontop of a linux install over a hypervisor vs nix on hardware.
- LtWorf 3y agoJust use a base OS that has what you need? :D
- zer00eyz 3y agoSO I should put my static go binary in a container, so you can deploy a static go binary to deploy the container with my static go binary in it. Do you see how many extra steps that is.
- ethanwillis 3y agoThis is the best joke I've heard all week. Standardized in what way? By who or what governing body?
- rmbyrro 3y agoWhy would someone want to self-torture into k8s if they only need a single machine? If you need isolation for multiple services, just use a container... I don't see an orchestration need that justifies using k8s on a single machine. For such context, it's too much hassle for very little value in return.
- zer00eyz 3y ago> cheaper than famous cloud instances Not just cheaper, fixed cost. Everyone who cried about exit fees on AWS needed the lesson of failing to plan ahead...
- api 3y agoYou can also have ugly manual ad hoc Kubernetes workflows where random devs hack YAML in prod directly. I’ve even seen people ssh into running containers and change things. This isn’t any better than Joe sysadmin and could be worse since the complexity is higher and there’s a greater chance to do more damage with one change. Adding complexity makes bad process worse.