Why would you manage a server with Kubernetes in any case??
Because otherwise you have to use this! Or some other DIY gobbled together whatever. That's tongue in cheek but a pretty hard check too, imo. The thing of it is, I like kubernetes, I think you'd have to be mad to opt to re-figure this all out, to get adequate parity. But but but I do want there to be competition, evolution, I want people trying things. Usually though the competition is trying to do far less. When peo…
Show HN: Managing on-premise servers without Kubernetes
11–17 of 17 posts
Re: Show HN: Managing on-premise servers without Kubernetes
#12Earlier quoted context omitted.
Because otherwise you have to use this! Or some other DIY gobbled together whatever. That's tongue in cheek but a pretty hard check too, imo. The thing of it is, I like kubernetes, I think you'd have to be mad to opt to re-figure this all out, to get adequate parity. But but but I do want there to be competition, evolution, I want people trying things. Usually though the competition is trying to do far less. When peo…
I'm still lost on how Kube has anything to do with server management (as someone who used to be a sysadmin and manage many servers, maybe my definition is just different?). Kubernetes doesn't solve any of the problems this does, it is so far from anything I would reach for to "manage" anything.
Yes, you still need to something to "install" the Kubernetes but that is generally easier surface area with something like Talos OS, K3s, whatever Canonical/Red Hat cooked up.
Re: Show HN: Managing on-premise servers without Kubernetes
#13I have to ask why someone would choose this over ansible, ssh, and a proper monitoring and metrics stack. Something like this allows unconstrained config drift with no audit trail.
Re: Show HN: Managing on-premise servers without Kubernetes
#14Earlier quoted context omitted.
I'm still lost on how Kube has anything to do with server management (as someone who used to be a sysadmin and manage many servers, maybe my definition is just different?). Kubernetes doesn't solve any of the problems this does, it is so far from anything I would reach for to "manage" anything.
SRE here, when most people say "Server Management" they are talking the root of their problem. "I have this set of Applications and that need to run on this fleet of servers. How do I do this?" and Kubernetes is commonly the answer but not only answer. Yes, you still need to something to "install" the Kubernetes but that is generally easier surface area with something like Talos OS, K3s, whatever Canonical/Red Hat co…
Re: Show HN: Managing on-premise servers without Kubernetes
#15Earlier quoted context omitted.
SRE here, when most people say "Server Management" they are talking the root of their problem. "I have this set of Applications and that need to run on this fleet of servers. How do I do this?" and Kubernetes is commonly the answer but not only answer. Yes, you still need to something to "install" the Kubernetes but that is generally easier surface area with something like Talos OS, K3s, whatever Canonical/Red Hat co…
Kubernetes is only another application to me, it just manages containers (which probably run applications, which may be serving something, I guess?). Definitions have got a bit muddy since the advent of devops imo! (Maybe part of the weirdness is that this post is about an app that manages crons and files and other os-level stuff)
Re: Show HN: Managing on-premise servers without Kubernetes
#16I have to ask why someone would choose this over ansible, ssh, and a proper monitoring and metrics stack. Something like this allows unconstrained config drift with no audit trail.
Once you get big enough, Kubernetes for 99% of companies, is next logical step.
Re: Show HN: Managing on-premise servers without Kubernetes
#17Earlier quoted context omitted.
Kubernetes is only another application to me, it just manages containers (which probably run applications, which may be serving something, I guess?). Definitions have got a bit muddy since the advent of devops imo! (Maybe part of the weirdness is that this post is about an app that manages crons and files and other os-level stuff)
Sure, it's just another application technically. On more practical level, it's pretty much an OS.
But it's really a gradient. As more and more services and systems move from being systemd services (or whatever) to in kubernetes, I see it as the position along a gradient shifting. Both are operating systems. They're different operating systems, doing different things, but both manage and provide resources for user payloads, both run apps, both host a user interface (apiserver for kubernetes), both have state (also apiserver, vs file-systems).