1.8 KiB
1.8 KiB
Talos maintenance
Regular checks
talosctl --talosconfig=./generated/clusterconfig/talosconfig healthkubectl get nodesflux get all -Atalosctl -n <node-ip> version
Upgrade flow
- Update
talos_factory_schematic_id,talos_version, andtalos_iso_filein Terraform inputs. - If
talos_image_update_mode = "download", runterraform applyto stage the ISO on every target Proxmox node. - Regenerate machine config from
generated/talconfig.yaml:talhelper genconfig
- Upgrade one control plane node at a time:
talosctl upgrade --nodes <ip> --image factory.talos.dev/installer/<schematic>/<version>- wait for
talosctl health
- Upgrade workers one at a time.
- Refresh kubeconfig if needed:
talosctl kubeconfig --talosconfig=./generated/clusterconfig/talosconfig --nodes=<control-plane-ip> .
Certificate rotation
- Check cert expiry:
talosctl -n <control-plane-ip> get kubeapicerts,k8saggregatorca,etcdcerts
- Rotate before expiry during a maintenance window:
talosctl -n <control-plane-ip> rotate-catalosctl -n <control-plane-ip> rotate-certs
- After rotation, verify API and kubelet health on all nodes.
Disaster recovery basics
- Keep
generated/talsecret.sops.yamlencrypted and backed up. - Keep the rendered
generated/clusterconfig/talosconfigin a secure backup. - Capture an etcd snapshot before major upgrades:
talosctl -n <control-plane-ip> etcd snapshot ./etcd.snapshot
What to automate next
- PR automation that bumps Talos version + factory schematic outputs together.
- Scheduled
talosctl healthand cert expiry checks. - Optional automated image staging to all Proxmox nodes before upgrades.
- Optional upgrade orchestration that rolls one node at a time with health gates.