Why Fix Kubernetes and Systemd?
medium.com
Why Fix Kubernetes and Systemd?
1–10 of 120 posts
Re: Why Fix Kubernetes and Systemd?
#2If we do this "right" it kind of needs to go at the pace of the Kernel, and hold very tightly onto the API scope to protect the project from scope creep.
Re: Why Fix Kubernetes and Systemd?
#3how to fix this "most-open unit of computing" will depend on "what" do you think this 'unit of compute' even means, which of course depends on who you are and what do you do with 'units of compute' (buy? sell? resell? use up? build? oversee??)
Re: Why Fix Kubernetes and Systemd?
#4 Lack of Unix philosophy
[...]
Missing rest/gRPC/json API
OK ...Re: Why Fix Kubernetes and Systemd?
#5Re: Why Fix Kubernetes and Systemd?
#6That is sort of what we're talking about when we talk about unix philosophy. If your daemons for handling all those aren't tightly coupled then it's easier to use the same tools for different tasks.
Re: Why Fix Kubernetes and Systemd?
#7Re: Why Fix Kubernetes and Systemd?
#8Re: Why Fix Kubernetes and Systemd?
#9Re: Why Fix Kubernetes and Systemd?
#10Doesn't sound like this fixes systemd, unless your problem is that you depend on systemd + kubernetes. That is, I read this as a Redhat/Gnome/Freedesktop problem; I'd love a fix for systemd, but I don't think this one solves my problems.