Worth mentioning that Talos Linux features bit-for-bit reproducible builds and a full-source bootstrapped toolchain, which in my opinion should be featured everywhere. And sooner or later probably will.
For those of you who don’t know what that is I highly recommend to look it up.
In short build dag starts with (ai provided steps) a hand-written 181-byte i386 ELF (hex0) that just converts hex to bytes. It builds a hex assembler with labels, then a macro assembler, then a tiny C-subset compiler (M2-Planet), then GNU Mes, then TinyCC, then GCC 4.0.4. GCC then climbs through 4.7.4 (the last GCC written in C), 10 and 13. That GCC builds Go 1.4 (the last Go written in C), each Go release builds the next, and the final toolchain compiles the Linux kernel and the Talos binaries.
My team ran on-premise with Talos for the last bunch of years. It avoided tons of odd issues I saw when I built k8s clusters on top of Ubuntu that I never quite ironed out.
It gave me a ton of appreciation for Kubernetes and Linux and how k8s is built on linux assumptions: the file system layout’s a little different in Talos to the default k8s assumptions, so there were some small adjustments I’d make every now and then.
Sidero’s professional support is out of the world, too. I had simple questions and got answers back from their devops engineers who are running clusters 100-1000 times the size of anything I had to touch, or from their software engineering team who write Talos.
Definitely worth a look if you’re hosting in your home lab, definitely worth a look if you’re doing self-hosted k8s for your job.
Isn't k8s overkill for a home lab? I'm happily running my homelab on docker swarm, and don't miss anything from k8s. Tot the contrary, I think it would cost me some efforts only to convert compose files to deploy to kiss.
I'm asking because I haven't touched k8s for some years, maybe the situation has changed and I should re evaluate my choices?
Can't give enough praise to Talos. I run it both at home and at work. Depending on what you wanna play with in your home lab / hobby projects I can recommend their Omni Hobby Plan which was made free recently-ish to avoid having to host Omni.
Really looking forward to see their new "Director" product with the hypervisor support for running VM's as well. I hope the pricing is resonable enough that it is a feasible solution for companies I work with. Would be useful to use that for creating virtual k8s nodes, to slice the same physical hardware into more clusters.
(If Siderolabs are here, it would be awesome to be able to use Director as a hobbyist in the future as well - I think it's a great sales pipeline for you to allow enthusiasts play with it at home and pitch it to internal stakeholders)
You might want to check out what's on your network :-(. It works from here and the certificate was issued by LetsEncrypt in late October, expires late January. If you're seeing something different, you should look at what's between your browser and the site.
Running it on bare metal. Highly recommended for anyone who wants to own their infrastructure and reduce their exposure to the never-ending stream of security vulnerabilities.
I'd love to know some details on why? I don't have any particular complaints about my k3s on Debian, but if there is a better option, I would love to know!
I run it on bare metal since i only see downsides from having another VM layer around it. Just forego kvm and use linux containers. You can also use Talos/Kubernetes as a VM hypervisor through stuff like kata containers.
I do, still. It's often a lot cheaper and modern HW is very robust and reliable. But it comes with more responsibility, of course. Not happy with performance on typical cheap VMs.
Obviously, something is still being run on bare metal. One area of consulting for is right now moving people off of VMware who don’t feel like paying the rather stiff Broadcom licence fees.
With Kubernetes it makes a lot of sense to run bare metal. What advantage is there to running K8s nodes on a hypervisor? It's one more thing that requires maintenance and can go wrong.
And that's actually my concern with K8s still. It still has an unnecessarily high maintenance burden for projects that are limited in scope and few scalability requirements. Which can often still be an important project.
Often I find that a load balancer and a couple of docker compose file sis more rugged, because you'll be able to leave it for a year and it'll still work and easily be understood by just glancing at it.
Kubernetes will still work after a year too, it just won't be supported. I forgot about a K3s setup for well over a year...
If you don't need a cluster then a single node K3s is still better than Docker Compose. You might know how an ad hoc load balancer and Docker Compose works, but I wouldn't say this knowledge is any more given than knowing K8s these days.
But if you do need a cluster then maintaining a bunch of Talos nodes is easier than maintaining a bunch of full fat GNU/Linux boxen tbh.
I've never looked at K3s so this is intriguing. I find docker compose great but it lacks some things that add to the complexity if bolting on, e.g. secrets management, or even load balancing on the single node to achieve zero downtime deployments. Would k3s handle the proxy layer?
IMO a lot of the "K8s is complex" is just the fact that you _can_ go complex with it, but you can really just declare pods and stuff and avoid the abstractions
I feel like k8s is better as soon as your thing goes from simple self-contained thing to multiple things running on one box
especially with agents it's never been easier to work with k8s.
from my experience, k3s supports basically everything k8s has that you'd need for a single-node setup
not sure what "Would k3s handle the proxy layer" means but if you mean the load-balancing part, then yes, that's like one of the main abstractions that k8s provides. but again, it provides many knobs so you probably just wanna pick the simplest option available
I do :)
alongside cloud of course, hybrid is the way to go in my view.
I run a bunch of openshift clusters for very private container workloads and VMs.
You can't beat a local fiber channel SAN for speed and reliability, especially compared to cloud software defined storage, and even on the networking side of things if you worked out your local connectivity well using real networking vs cloud providers software defined networks is so much better.
CSIs are hit and miss, some vendors are really really good, some are meh (hitachi, even though they are improving a lot with the latest relases), but the moment you get an IBM nvme san and start to tune all layers you get performance that are out of this world, some of our dbms workloads are very io sensitive and they improved 10x with nvme fabric.
You'd think someone with a "talk to us" enterprise plan and a bunch of well known brands as customers would have at least one human copytexter and a designer on staff. Instead, a landing page reeking of Claudish in text and look.
talosctl debug docker.io/library/alpine:3.24 gives you a shell in the host namespaces, with root mounted at /host. I think it works without kubelet, I suppose it might not help with a failed containerd though.
Worth mentioning that Talos Linux features bit-for-bit reproducible builds and a full-source bootstrapped toolchain, which in my opinion should be featured everywhere. And sooner or later probably will.
For those of you who don’t know what that is I highly recommend to look it up.
In short build dag starts with (ai provided steps) a hand-written 181-byte i386 ELF (hex0) that just converts hex to bytes. It builds a hex assembler with labels, then a macro assembler, then a tiny C-subset compiler (M2-Planet), then GNU Mes, then TinyCC, then GCC 4.0.4. GCC then climbs through 4.7.4 (the last GCC written in C), 10 and 13. That GCC builds Go 1.4 (the last Go written in C), each Go release builds the next, and the final toolchain compiles the Linux kernel and the Talos binaries.
My team ran on-premise with Talos for the last bunch of years. It avoided tons of odd issues I saw when I built k8s clusters on top of Ubuntu that I never quite ironed out.
It gave me a ton of appreciation for Kubernetes and Linux and how k8s is built on linux assumptions: the file system layout’s a little different in Talos to the default k8s assumptions, so there were some small adjustments I’d make every now and then.
Sidero’s professional support is out of the world, too. I had simple questions and got answers back from their devops engineers who are running clusters 100-1000 times the size of anything I had to touch, or from their software engineering team who write Talos.
Definitely worth a look if you’re hosting in your home lab, definitely worth a look if you’re doing self-hosted k8s for your job.
Isn't k8s overkill for a home lab? I'm happily running my homelab on docker swarm, and don't miss anything from k8s. Tot the contrary, I think it would cost me some efforts only to convert compose files to deploy to kiss.
I'm asking because I haven't touched k8s for some years, maybe the situation has changed and I should re evaluate my choices?
To me, the whole point of home labbing was to learn, so nothing was really "overkill" in that sense. K8s was highly in-demand so that's what I used.
Now if your home lab priority is to run a plex server for your family and you rarely want to touch the lab, then yes k8s is likely overkill.
A homelab itself is overkill, but the point is to learn.
I run my stuff on Ubuntu minimal with K3S, it was a fun journey to learn about k8s and related software (Argo,Renovate, CNPG etc..)
Can't give enough praise to Talos. I run it both at home and at work. Depending on what you wanna play with in your home lab / hobby projects I can recommend their Omni Hobby Plan which was made free recently-ish to avoid having to host Omni.
Really looking forward to see their new "Director" product with the hypervisor support for running VM's as well. I hope the pricing is resonable enough that it is a feasible solution for companies I work with. Would be useful to use that for creating virtual k8s nodes, to slice the same physical hardware into more clusters.
(If Siderolabs are here, it would be awesome to be able to use Director as a hobbyist in the future as well - I think it's a great sales pipeline for you to allow enthusiasts play with it at home and pitch it to internal stakeholders)
Can you explain why I'd use Talos over something like Fly.io for home projects?
Is anyone working on Talos without the k8s requirement? A minimal, API-driven OS is ideal, but requiring k8s is a weird stipulation.
Systemd is essentially growing in this direction but surprised there isn’t something out there already.
Yes, work is being done on both running containers without kubernetes and on hypervising other VMs on Talos.
Talos Containers: Running Containers Without Kubernetes | TalosCon Amsterdam 2026 https://youtu.be/xe_-upvfp5s
talos-hypervisor https://www.siderolabs.com/talos-hypervisor
Talos is bootstrapped with the Stagex toolchain which can build any image you want with or without k8s. https://stagex.tools (I am a maintainer)
I'm getting an SSL error when trying to connect to that site :(
You might want to check out what's on your network :-(. It works from here and the certificate was issued by LetsEncrypt in late October, expires late January. If you're seeing something different, you should look at what's between your browser and the site.
Running it on bare metal. Highly recommended for anyone who wants to own their infrastructure and reduce their exposure to the never-ending stream of security vulnerabilities.
I have set up Talos for self hosting to replace my old Ansible based approach. It was amazing and I didn't have a single issue.
In the end I moved away from k8s to nixos for my self hosted services, but if I ever need k8s again I'll go back straight to talos
What's the point of a linkdrop like this? Is there news regarding Talos? If so it's not on their site.
Switched to Talos from one k3s on Debian and Ubuntu, haven’t looked back even once.
I'd love to know some details on why? I don't have any particular complaints about my k3s on Debian, but if there is a better option, I would love to know!
How is this compare to balenaos for running on the edge rather than on a server?
Is it recommended to run Talos inside a VM or on bare metal or maybe it doesn't matter?
I’ve run it both ways, with virtualbox and vmware as a hypervisor, and with micro PCs as hardware.
I run it on bare metal, but both are viable.
I run it on bare metal since i only see downsides from having another VM layer around it. Just forego kvm and use linux containers. You can also use Talos/Kubernetes as a VM hypervisor through stuff like kata containers.
That doesn't really matter. I don't really know anyone who still runs anything on bare metal.
I do, still. It's often a lot cheaper and modern HW is very robust and reliable. But it comes with more responsibility, of course. Not happy with performance on typical cheap VMs.
Obviously, something is still being run on bare metal. One area of consulting for is right now moving people off of VMware who don’t feel like paying the rather stiff Broadcom licence fees.
With Kubernetes it makes a lot of sense to run bare metal. What advantage is there to running K8s nodes on a hypervisor? It's one more thing that requires maintenance and can go wrong.
And that's actually my concern with K8s still. It still has an unnecessarily high maintenance burden for projects that are limited in scope and few scalability requirements. Which can often still be an important project.
Often I find that a load balancer and a couple of docker compose file sis more rugged, because you'll be able to leave it for a year and it'll still work and easily be understood by just glancing at it.
Kubernetes will still work after a year too, it just won't be supported. I forgot about a K3s setup for well over a year...
If you don't need a cluster then a single node K3s is still better than Docker Compose. You might know how an ad hoc load balancer and Docker Compose works, but I wouldn't say this knowledge is any more given than knowing K8s these days.
But if you do need a cluster then maintaining a bunch of Talos nodes is easier than maintaining a bunch of full fat GNU/Linux boxen tbh.
I've never looked at K3s so this is intriguing. I find docker compose great but it lacks some things that add to the complexity if bolting on, e.g. secrets management, or even load balancing on the single node to achieve zero downtime deployments. Would k3s handle the proxy layer?
IMO a lot of the "K8s is complex" is just the fact that you _can_ go complex with it, but you can really just declare pods and stuff and avoid the abstractions
I feel like k8s is better as soon as your thing goes from simple self-contained thing to multiple things running on one box
especially with agents it's never been easier to work with k8s.
from my experience, k3s supports basically everything k8s has that you'd need for a single-node setup
not sure what "Would k3s handle the proxy layer" means but if you mean the load-balancing part, then yes, that's like one of the main abstractions that k8s provides. but again, it provides many knobs so you probably just wanna pick the simplest option available
> means but if you mean the load-balancing part, then yes, that's like one of the main abstractions that k8s provides.
Yeah that's what I thought. Perhaps just put HAProxy in front and then let k3s know about it?
I do :) alongside cloud of course, hybrid is the way to go in my view.
I run a bunch of openshift clusters for very private container workloads and VMs.
You can't beat a local fiber channel SAN for speed and reliability, especially compared to cloud software defined storage, and even on the networking side of things if you worked out your local connectivity well using real networking vs cloud providers software defined networks is so much better.
CSIs are hit and miss, some vendors are really really good, some are meh (hitachi, even though they are improving a lot with the latest relases), but the moment you get an IBM nvme san and start to tune all layers you get performance that are out of this world, some of our dbms workloads are very io sensitive and they improved 10x with nvme fabric.
Talos is great. But the website copy sucks so hard. They should have a human edit it.
Talos is awesome.
Talos is amazing, I cannot recommend it enough
Surely this should suppport PowerVM?
Popupssss
You'd think someone with a "talk to us" enterprise plan and a bunch of well known brands as customers would have at least one human copytexter and a designer on staff. Instead, a landing page reeking of Claudish in text and look.
Jesus.
Their designs been like that for a good few years, don’t think they used AI for the design.
If it weren’t written by Claude, then I think we’ve found the original training set that created Claudespeak.
This is written by claude, I can tell because when I read it, every word makes me want slapping someone in the face — not in the neck.
I can tell because my brain instantly tunes it out as low value and not worth reading.
At this point it’s a reflex and I race to the HN comments section to find something actually worth reading.
Talos is nice but debugging a failed kubelet without shell access is rough, spent way too long on serial console logs once
talosctl debug docker.io/library/alpine:3.24 gives you a shell in the host namespaces, with root mounted at /host. I think it works without kubelet, I suppose it might not help with a failed containerd though.
Nice to see an real apllication of unikernels. It looks promising!
Talos uses a customised linux kernel which runs `machined` as the `init` PID 1 process. The core Talos process runs in user-space.
Talos does not seem to be a unikernel. Just a distro with enough to run kubernetes and a management API.
It's not a unikernel.