The company behind Talos Linux has been acquired by Yardi (of WeWork fame).
I use Talos for my homelab and have been considering using it for work. I'm a little worried about the future direction. I'm not sure why they want to add VMs as a native resource rather than going in the direction of KubeVirt as a first class citizen (which already worked well).
This is a surprising development. I wonder how much of it was opportunistic, since Talos 1.14 added sandbox isolation based on Linux namespaces (?). Perhaps the reasoning was "let's just go one step further and support full containers/VMs instead of inventing our own sandbox mechanism".
We are running Abejora on a Talos Kubernetes cluster. Siderob Labs frames the acquisition as it were a good thing.
I'm not completely convinced.
If the Sidero Labs is doing well, then why would they need the acquisition? And if the Sidero Labs is not doing well, then why would Yardi keep the status quo?
The acquisition provides a lot of additional backing and security to expand our toolset/staff rapidly, something we couldn't do quickly through organic growth alone. Yardi, as an interested customer in our product and our ethos, felt it a good way to accelerate what we could offer to the world.
hm, a hypervisor too? Feels like something inbetween Openshift and Proxmox for a VMware replacement. Feels like that is the most obvious GTM, they have an immutability play that is probably interesting for edge-type nodes.
The company behind Talos Linux has been acquired by Yardi (of WeWork fame).
I use Talos for my homelab and have been considering using it for work. I'm a little worried about the future direction. I'm not sure why they want to add VMs as a native resource rather than going in the direction of KubeVirt as a first class citizen (which already worked well).
Kubevirt sounds like a great idea to a k8s admin and an absolutely insane idea to a VM admin... There's got to be a better way!
This is a surprising development. I wonder how much of it was opportunistic, since Talos 1.14 added sandbox isolation based on Linux namespaces (?). Perhaps the reasoning was "let's just go one step further and support full containers/VMs instead of inventing our own sandbox mechanism".
We are running Abejora on a Talos Kubernetes cluster. Siderob Labs frames the acquisition as it were a good thing.
I'm not completely convinced.
If the Sidero Labs is doing well, then why would they need the acquisition? And if the Sidero Labs is not doing well, then why would Yardi keep the status quo?
The acquisition provides a lot of additional backing and security to expand our toolset/staff rapidly, something we couldn't do quickly through organic growth alone. Yardi, as an interested customer in our product and our ethos, felt it a good way to accelerate what we could offer to the world.
- Chris, VP Sales & CX at Sidero Labs
Whilst I do like both hypervisors and talos k8s the thought of a hybrid doesn’t fill me with joy
I'm using Talos Linux in production (well 12 nodes, but still production) and I'm very happy with it. Hopefully it stays that way...
We hope so too! Let us know if you're finding it doesn't!
hm, a hypervisor too? Feels like something inbetween Openshift and Proxmox for a VMware replacement. Feels like that is the most obvious GTM, they have an immutability play that is probably interesting for edge-type nodes.
Very astute ;)
- VP sales & cx at Sidero Labs