<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>go on A cup of coffee</title><link>https://a-cup-of.coffee/tags/go/</link><description>Recent content in go on A cup of coffee</description><generator>Hugo -- gohugo.io</generator><copyright>Copyright © 2024</copyright><lastBuildDate>Fri, 10 Apr 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://a-cup-of.coffee/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>talosctl-oidc: adding SSO to Talos Linux</title><link>https://a-cup-of.coffee/blog/talosctl-oidc/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0200</pubDate><guid>https://a-cup-of.coffee/blog/talosctl-oidc/</guid><description>If you follow my blog regularly, you know I have a genuine fondness for Talos Linux. It&amp;rsquo;s the OS I recommend without hesitation for running Kubernetes: immutable, minimalist, SSH-free, with a gRPC API for all administration. In short, it&amp;rsquo;s what a cloud-native OS should be.
But there&amp;rsquo;s one thing that has always bothered me a little: authentication. Talos uses mTLS (mutual TLS) to protect its API. In practice, for a user to run talosctl, they need a client certificate signed by the Talos CA.</description></item></channel></rss>