3 ms·

I’m actually a big fan of systemd. It’s an awesome, general purpose, and flexible init system. I don’t think the complexity it brings is required for Kubernete

• tehbeard 3y ago
  it could have been said without the x lines of code comment. "lines of code" is so often used as a "disparagement" about software rather than a metric for understandability. Something along the lines of "...not needing a general purpose init system that integrates with logging, network and mounting, when all we are running is Kubernetes."
• hosh 3y ago
  There's work in a new kublet replacement that moves things that would normally go into daemonset into systemd (or something like systemd). There's also a neat feature of podman that runs pods as systemd units, which is a nice intermediate step between a more traditional pet server and a full kubernetes cluster.
  • cpuguy83 3y ago
    https://github.com/cpuguy83/containerd-shim-systemd-v1 https://github.com/cpuguy83/containerd-shim-systemd-v1 to do this with containerd.
    • hosh 3y ago
      Also this one: https://github.com/virtual-kubelet/systemk https://github.com/virtual-kubelet/systemk Although what I was thinking of was an article written somewhere and posted here in HN, and more a broad rethink on Kubernetes.
• hughesjj 3y ago
  The second I learned how to write systems unit files was the second I evicted initv/rc.d scripts from my mind. Well, okay, from my search terms at least ;-) It can even kind of replace cron with timers, and no more mucking with grub. Also, true parallel init tasks. Love it.