Skip to content

Commit

Permalink
docs: add how-to for cert management
Browse files Browse the repository at this point in the history
Explain certificate auto-rotation.

Signed-off-by: Steve Francis <steve.francis@talos-systems.com>
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
  • Loading branch information
steverfrancis authored and smira committed Jan 18, 2024
1 parent b0ee0bf commit 3911ddf
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions website/content/v1.6/talos-guides/howto/cert-management.md
@@ -0,0 +1,14 @@
---
title: "How to manage certificate lifetimes with Talos Linux"
aliases:

---

Talos Linux automatically manages and rotates all server side certs for etcd, Kubernetes, and the Talos API.
Note however that the kubelet needs to be restarted at least once a year in order for the certificates to be rotated.
Any upgrade/reboot of the node will suffice for this effect.

Client certs (`talosconfig` and `kubeconfig`) are the user's responsibility.
Each time you download the `kubeconfig` file from a Talos Linux cluster, the client certificate is regenerated giving you a kubeconfig which is valid for a year.

The `talosconfig` file should be renewed at least once a year, using the `talosctl config new` command.

0 comments on commit 3911ddf

Please sign in to comment.