4 ms·

You 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 ago
Your 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 ago
  kubernetes is also a static go binary (kubelet) deployed with systemd!
  - hparadiz 3y ago
    Why use k8s over just a docker container?
    - zer00eyz 3y ago
      Dont deploy docker in production. Podman. You could but why all the extra overhead?
      - hparadiz 3y ago
        Docker 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 ago
        The 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 ago
      Just use a base OS that has what you need? :D
      - hparadiz 3y ago
        Was asking seriously. Haven't had the opportunity to use k8s but I've used container hosting elsewhere so I'm curious why k8s specifically.
      - pdimitar 3y ago
        Yes, do that 99% of the time actually.
  - zer00eyz 3y ago
    SO 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 ago
This is the best joke I've heard all week. Standardized in what way? By who or what governing body?
rmbyrro 3y ago
Why 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

Your 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 ago
kubernetes is also a static go binary (kubelet) deployed with systemd!
- hparadiz 3y ago
  Why use k8s over just a docker container?
  - zer00eyz 3y ago
    Dont deploy docker in production. Podman. You could but why all the extra overhead?
    - hparadiz 3y ago
      Docker 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 ago
        The 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 ago
    Just use a base OS that has what you need? :D
    - hparadiz 3y ago
      Was asking seriously. Haven't had the opportunity to use k8s but I've used container hosting elsewhere so I'm curious why k8s specifically.
    - pdimitar 3y ago
      Yes, do that 99% of the time actually.
- zer00eyz 3y ago
  SO 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 ago

This is the best joke I've heard all week. Standardized in what way? By who or what governing body?

rmbyrro 3y ago

Why 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.