What CI/CD tools work well with Talos Linux clusters?

If your repositories are on GitHub, take a look at GitHub Actions with Actions Runner Controller. It gives you Kubernetes-hosted runners for workflows without having to build a separate pipeline system around your existing CronJobs.

Check the image build method and runner permissions before rolling it out broadly. The runner being able to start on Talos doesn't guarantee every build tool or privileged workload will work unchanged.

Argo Workflows is worth a look for the scheduled Ansible side. It runs workflows on Kubernetes and supports scheduled workflows, so you could define jobs without maintaining a separate CronJob template for each one.

Flux can still handle application deployment while the workflow system handles tasks. I'd test the Ansible execution environment and cluster credentials first, especially if playbooks need access to different clusters.

For a less GitHub-specific option, check out Tekton. It's a Kubernetes-native pipeline system and could cover the build and push jobs as well as other containerized tasks. You'll still need to evaluate scheduling and the tooling around it for your playbooks.

AWX is another option if scheduled Ansible is the main headache. The AWX Operator deploys it on Kubernetes, and AWX is focused on running and scheduling playbooks rather than being a general-purpose image build system.

You could use it alongside a separate CI tool instead of forcing both jobs into one product. That does mean another service to maintain, though.

I wouldn't assume the Concourse problem means Talos rules out CI tools in general. The tricky bit may be how a particular worker or image builder uses the container runtime and privileged access.

For any candidate, try a small proof of concept on Talos with an actual image build and a scheduled playbook. Check its security requirements before committing to a production rollout.