4 ms·

You don't need a whole cluster to get started, you can use Minikube locally for example : https://minikube.sigs.k8s.io/docs/ https://minikube.sigs.k8s.io/docs/

katsura 7y ago
Have they solved the high CPU usage problem while it is running (even when no containers are inside)? I don't like my laptop hot, so never could make a switch.
- ngrilly 7y ago
  Yes, it's a real issue. Kubernetes burns too much RAM and CPU even with no workload.
  - Fnoord 7y ago
    Docker on macOS also suffers from that issue though.
    - mschuster91 7y ago
      Not for me, except for the RAM blocking - I wish that Hyperkit could dynamically allocate and release RAM for the guest machine instead of blocking 2GB (in my case) by default all the time.
    - ngrilly 7y ago
      I haven't noticed that.
    - GordonS 7y ago
      It will use more on MacOS and Windows than on Linux, as it needs to use a sidecar Linux "Moby" VM to run containers. In practice on Windows, this hasn't been an issue for me (64GB RAM in my dev laptop). This will actually finally change soon'ish with Windows at least, I think as part of WSL2. Not sure if anything is going to change on MacOS.
- ypcx 7y ago
  They haven't. As an example of where this lack of efficiency comes from, recently I've fixed an issue during which I've discovered that the Etcd component of k8s uses periodic (10 sec) liveness checking, where for every check (launching of the etcdctl client), the `runc` binary (from container.d) is executed 3 (three) times. You can imagine this probably just scratches the surface.
  - ngrilly 7y ago
    Ugh! Was the fix committed upstream?
    - ypcx 7y ago
      Yes, this one was a systemd detection in runc, which was causing big log flooding and runtime overhead due to runc being executed so frequently. I initially cached the checks, but later the devs removed them altogether. Still, this is not solving the inefficiencies in k8s. https://github.com/kubernetes/kubernetes/issues/76531 https://github.com/kubernetes/kubernetes/issues/76531
- bryanlarsen 7y ago
  --vm-driver=none helps a lot with the CPU and especially RAM usage, using k3s instead of minikube helps more.
jhanschoo 7y ago
If uptime is not a concern and only one node is intended, docker-compose is a far more efficient solution to any k8s solution.
- Majestic121 7y ago
  It might be more efficient but it's definitely not a solution to get up to speed with k8s
  - jhanschoo 7y ago
    I'm sorry, I somehow missed that the top-level commenter was interested in the one-node k8s to get started in it.

katsura 7y ago

Have they solved the high CPU usage problem while it is running (even when no containers are inside)? I don't like my laptop hot, so never could make a switch.

ngrilly 7y ago
Yes, it's a real issue. Kubernetes burns too much RAM and CPU even with no workload.
- Fnoord 7y ago
  Docker on macOS also suffers from that issue though.
  - mschuster91 7y ago
    Not for me, except for the RAM blocking - I wish that Hyperkit could dynamically allocate and release RAM for the guest machine instead of blocking 2GB (in my case) by default all the time.
  - ngrilly 7y ago
    I haven't noticed that.
  - GordonS 7y ago
    It will use more on MacOS and Windows than on Linux, as it needs to use a sidecar Linux "Moby" VM to run containers. In practice on Windows, this hasn't been an issue for me (64GB RAM in my dev laptop). This will actually finally change soon'ish with Windows at least, I think as part of WSL2. Not sure if anything is going to change on MacOS.
ypcx 7y ago
They haven't. As an example of where this lack of efficiency comes from, recently I've fixed an issue during which I've discovered that the Etcd component of k8s uses periodic (10 sec) liveness checking, where for every check (launching of the etcdctl client), the `runc` binary (from container.d) is executed 3 (three) times. You can imagine this probably just scratches the surface.
- ngrilly 7y ago
  Ugh! Was the fix committed upstream?
  - ypcx 7y ago
    Yes, this one was a systemd detection in runc, which was causing big log flooding and runtime overhead due to runc being executed so frequently. I initially cached the checks, but later the devs removed them altogether. Still, this is not solving the inefficiencies in k8s. https://github.com/kubernetes/kubernetes/issues/76531 https://github.com/kubernetes/kubernetes/issues/76531
bryanlarsen 7y ago
--vm-driver=none helps a lot with the CPU and especially RAM usage, using k3s instead of minikube helps more.

jhanschoo 7y ago

If uptime is not a concern and only one node is intended, docker-compose is a far more efficient solution to any k8s solution.

Majestic121 7y ago
It might be more efficient but it's definitely not a solution to get up to speed with k8s
- jhanschoo 7y ago
  I'm sorry, I somehow missed that the top-level commenter was interested in the one-node k8s to get started in it.