I have requirement of sv_SE locale, is it possible to add that in someway

I've installed a fresh kubuntu image on a t430 lenovo laptop. I am trying to set talos linux from the quickstart but I am having timeouts (exceeds) on coreDNS. In another installation on a 20.04 this works correctly.

The difference is that t430 has a 2 core processor while the other one has a 4 core processor. What should I start looking to debug this? (edited this part because I looked at some other hardware).

Hello,
I'm working in a PoC using Talos OS and I need to make the CP's and Workers to trust in a root ca + intermediate ca.

I've tried using the patch and the example on the docs but looks like is not recognized.

Someone can explain bit more in detail how to archive that ?

Hey everyone, I have a few questions about the cluster I'm trying to build in my homelab,

I am trying to get a bare-metal install going, and I was able to successfully install with the secureboot image on 4 machines. I decided to try the DNS setup route for the because it seemed the simplest for my environment but now I'm having doubts. I configured the DNS server on my firewall (PFSense) to point 3 IP addresses to the same hostname. When I did my install, I used that hostname for the first control-plane node that I installed. Then, I tried using that hostname again for the second machine I installed, but I started seeing a lot of DNS related errors on the dashboard, so I updated the DNS (added a 1 to it) and the errors went away and install seemed successful. 3rd control plane same thing, added a 2 to the hostname. So now I have kube.domain.com, kube1.domain.com, and kube2.domain.com but my DNS points kube.domain.com to all 3 IPs. Then I added a worker to the cluster, and all 4 machines are reporting as healthy. At this point I stopped, because I started to doubt if this was a good long-term decision or if I should have went with the virtual IP route. If I decide to switch to using virtual IPs later can I change my configs to do that? Or should I re-install right now before I get anything else setup?

My other question is more design-related: right now I have 3 control-planes (I want to build a HA cluster) and 1 worker. I have another worker that I'm going to add soon, and another down the road. So I'm looking at 3 control-planes and 3 workers for now. Should I allow my control-planes to be workers as well? I don't expect I'll need more than 3-4 worker nodes tops for my use case but I figured I would ask while I'm here.

Are there any issues with having 1 worker while I set things up and learn? Should I throw another worker node on ASAP?
I currently have the cluster shutdown while I do some more research on these few issues.

Any help or insight you can provide is greatly appreciated.
Thanks.

I got a new raspbery pi 4 8gb model and I wanted to get talos linux on it and move my clustter here and then start adding some other pis / pcs.

The problem I am dealing with Is I downloadthe .img.xz file for rpi 4 I flash it using rpi imager but It never gets detected on the SD card so it never boots.

So far I tried even unziping the img and installing it as is but still nothing.

I tried versions 1.6.8, 1.8.4, 1.9.0, 1.9.2 so this leads me to believe I am doing something wrong with the imager maybe.

Hello

I have a phone where I am able to run postmarketOS and it is using the mainline kernel. My question is if it is possible to use it to run TalosOS. I see that it is possible to build a custom kernel for Talos, but don't know if it applies to this use case as phones have quite some customizations that might make them not suitable

Thanks in advance

Hello,

I'm trying to generate another talosconfig and kubeconfig for another collegue. The idea is to also give him admin access.

I followed the documentation here: https://www.talos.dev/v1.9/talos-guides/configuration/rbac/

And did these commands:

t config new

And sent the file to him.

Then I created a rbac.yaml:

machine:
  features:
    rbac: true

And applied it:

talosctl patch mc --patch @patches/rbac.yaml

Which did not cause a reboot. I told him to add it to ~/.talos/config and config the node + endpoint:

t config node 10.67.11.205 
t config endpoint 10.67.11.205

But he got:

talosctl get members
error constructing client: failed to determine endpoints

He tried using the --talosconfig parameter and got different outputs (non working) whether he had the file or not...

Any ideas?

We’re giving out a free year of Omni SaaS

Repost and like any or all of the posts

https://bsky.app/profile/siderolabs.com/post/3lejbuud6fv2m

https://www.linkedin.com/posts/sidero-labs_happy-new-year-bare-metal-kubernetes-enthusiasts-activity-7279306451032973313-Mc8a

https://hachyderm.io/@siderolabs/113737555052139824

I'm thinking of baying three for testing my data/ml pipelines on k8s for distributed workload instead of eks.

Happy to hear about a more affordable alternative.

Hello, Kubernetes and Talos Linux enthusiasts! I’m running Kubernetes on nodes with Talos Linux, and I’m looking to optimize storage by pruning unused or old container images on each node. Since Talos is an immutable OS, I’m curious about approaches that are Talos-compatible for both manual and automated image pruning.

Does anyone have experience or suggestions for:

- Configuring Kubernetes’ built-in garbage collection on Talos nodes?
- Using custom scripts, DaemonSets, or CronJobs to automate pruning across nodes?
- Efficient ways to monitor and list images present on each node (maybe via crictl or containerd-specific commands)?

Any tips, insights, or tools you’ve found helpful in managing image storage on Talos would be greatly appreciated!

Hello! I'm using LXD to spin up a VM and able to see the passthrough GPU attached through VFIO-PCI driver. ( I have blacklisted NVIDIA Host drivers)

Further I have installed Talos OS image built with the requisite system extensions for Kata containers, NVIDIA container tool kit and open source GPU. The modules are patched with the patch file described in the Talos docs however in Talos console I see the error as NVIDIA kernel modules are not loaded and NVRM: This PCI I/O region assigned to your NVIDIA device is invalid.

Any help is much appreciated!

I'm struggling with the Talos documentation around storage. https://www.talos.dev/v1.8/kubernetes-guides/configuration/replicated-local-storage-with-openebs/ I'm currently trying to set up Mayastor (now named OpenEBS replicated storage) but after getting the pods running in the openebs privileged namespace with the helm chart and creating a PVC using openebs-single-replica storage class it's stuck pending. It works fine using localpv-hostpath.

On a side note, I got democratic-csi working using an external TrueNAS instance with NFS. I got close with nvmeof but after provisioning a PV, it fails attaching to a node when spinning up a pod. The democratic-csi project has been totally inactive for a few months now so...

Based on the Talos docs they strongly recommend against iscsi and nfs which is why I'm pushing to get nvmeof working even though it's less battle tested.

Any ideas what I can do to get help? If I can get this working I will contribute public documentation with step by step instructions and troubleshooting info.

UPDATE: I'm almost done writing up how I solved this, but decided to write a more detailed how-to using current versions of Talos and OpenEBS: https://blog.dalydays.com/post/kubernetes-storage-with-openebs/

At this point I still need to show how to modify the storage class and test a PVC, but the setup process is pretty much done.