If there are any folks here from Talos, I think there's a lot of confusion about what it is, where it fits in the stack and so on. I think part of the confusion comes from the scarcity of diagrams. I personally also find it helpful to have design motivations laid out. There is a list of "capabilities and benefits", but it would help me to understand what the current state of the world before Talos is added to it.
Hi. I am writing up a response now :)
Talos: OS for Kubernetes
31–40 of 79 posts
Re: Talos: OS for Kubernetes
#32Re: Talos: OS for Kubernetes
#33Somehow When I read "OS for Kubernetes" I thought it was yet one more layer of abstraction on top of Kubernetes.
Re: Talos: OS for Kubernetes
#34It took me a lot of reading before understanding that this is an OS on which you run a Kubernetes node//master and not a so-called OS on top of Kubernetes. Somehow When I read "OS for Kubernetes" I thought it was yet one more layer of abstraction on top of Kubernetes.
Re: Talos: OS for Kubernetes
#35You had me at "a modern"
Re: Talos: OS for Kubernetes
#36Can somebody give me(/HN) a TL;DR of how this differs from existing OSs targeted for Kubernetes, like GCP's Container-Optimized OS? https://cloud.google.com/container-optimized-os/ The big difference seems to be removing SSH. I understand the theoretical rationale, but in practice it seems like this would complicate troubleshooting quite a bit. Yes, maybe you shouldn't be SSHing into prod ever, but how do you keep th…
The difference here is that Talos is purpose-built for Kubernetes. What that means is that we will pour resources into automated upgrades paths for our users. Tighter integration with Kubernetes, where we envision a self-healing system that makes use of the Kubernetes and Talos APIs to make decisions.
Also the things I mentioned in https://news.ycombinator.com/item?id=21066732
Re: Talos: OS for Kubernetes
#37Earlier quoted context omitted.
Hi. I am writing up a response now :)
FYI: Talos is a trademarked name. In tech. So is Telos. This will be very confusing and likely cause you issues
Re: Talos: OS for Kubernetes
#38It took me a lot of reading before understanding that this is an OS on which you run a Kubernetes node//master and not a so-called OS on top of Kubernetes. Somehow When I read "OS for Kubernetes" I thought it was yet one more layer of abstraction on top of Kubernetes.
Ahh thanks for the feedback. One thing is clear from all this is that we can do a better job in documentation.
I have passed on countless products when evaluating solutions for having very flashy sales pages with no actual description of the product itself. "Improve your ROI! Decrease Downtime!" aren't features, per se, but potential benefits that can only be determined if the product is a fit, and I can only determine fit if I know that the hell it does.
/rant
Re: Talos: OS for Kubernetes
#39Earlier quoted context omitted.
Ahh thanks for the feedback. One thing is clear from all this is that we can do a better job in documentation.
I wish these sales-type pages had a "click here if you're an engineer." The page would contain a buzzword-free, straightforward explanation of what the product's purpose is, what its major features are, and what interfaces are exposed for control and flow. I have passed on countless products when evaluating solutions for having very flashy sales pages with no actual description of the product itself. "Improve your RO…
Re: Talos: OS for Kubernetes
#40Hey folks, Talos creator here. Happy to answer any questions you guys may have. Sounds like some confusion about exactly what Talos is. A lot of good feedback here that we will take and improve our documentation. Talos is a Linux distribution built specifically for Kubernetes. The short version is that we have stripped out absolutely everything that is not required to make a machine a Kubernetes node, including SSH a…
I see immutable, but also upgradable? Is that via in-place upgrades or do upgrades require a reboot?
Example: severe bug or vulnerability in kubelet or containerd/docker. Can I use the API to roll out a fix to existing nodes such that running workloads have no disruption?