kubernetes upgrade

DevOps Community

Skill notes

Quick Reference

Item · Value Upgrade command · talosctl upgrade-k8s -n <cp-node> --to v<version> Config file · talos/talconfig.yaml (kubernetesVersion field) Node topology · 3 CP (e2-1/2/3), 3 workers (ms-01-1/2/3) Talos OS agent · talos-upgrade (different from this skill)

Phase 1: Input Parsing

Parse target version from user message; prompt if missing Read current version from talos/talconfig.yaml (kubernetesVersion) Classify: minor (1.34→1.35, higher risk) or patch (1.35.0→1.35.1)

Phase 2: Create GitHub Issue

Create a GitHub issue using the infra template so SRE agents see maintenance context. Include: Title: infra(k8s): upgrade Kubernetes to v<version> Label: infra Summary, motivation (Renovate PR ref if applicable), planned changes, rollback plan, risk level (patch vs minor) Track issue number for commit references (Ref #<number>)

Phase 3: Breaking Changes Research

Consult references/breaking-changes-lookup.md for procedures. HARD GATE: Present findings. Wait for user acknowledgment. If removed APIs match cluster resources, recommend aborting.

Phase 4: Cluster API Compatibility Scan

Consult references/api-deprecation-scanning.md for procedures. HARD GATE: If removed APIs are in active use, BLOCK. List resources requiring migration.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Linux
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Input Parsing

Parse target version from user message; prompt if missing Read current version from `talos/talconfig.yaml` (`kubernetesVersion`) Classify: minor (1.34→1.35, higher risk) or patch (1.35.0→1.35.1)

02
Phase 2: Create GitHub Issue

Create a GitHub issue using the `infra` template so SRE agents see maintenance context. Include: Title: `infra(k8s): upgrade Kubernetes to v<version>` Label: `infra` Summary, motivation (Renovate PR ref if applicable), planned changes, rollback plan, risk level (patch vs minor) Track issue number for commit references (`Ref #<number>`)

03
Phase 3: Breaking Changes Research

Consult `references/breaking-changes-lookup.md` for procedures. HARD GATE: Present findings. Wait for user acknowledgment. If removed APIs match cluster resources, recommend aborting.

04
Phase 4: Cluster API Compatibility Scan

Consult `references/api-deprecation-scanning.md` for procedures. HARD GATE: If removed APIs are in active use, BLOCK. List resources requiring migration.

05
Phase 5: Talos Compatibility Check

Read Talos version from `talos/talconfig.yaml` (`talosVersion`) Query Context7: `query-docs(libraryId: "/siderolabs/talos", query: "supported kubernetes versions for Talos v<current>")` HARD GATE: If incompatible, BLOCK. Recommend `talos-upgrade` agent first.

06
Phase 6: Cluster Health Gate

Discover CP node IPs dynamically: Check · Command · Pass Criteria Nodes · `kubectl get nodes -o wide` · All Ready Talos health · `talosctl health -n <first-cp>` · Passes etcd · `talosctl etcd status -n <cp1>,<cp2>,<cp3>` · 3 healthy members

07
Phase 7: etcd Backup

Phase 7: etcd Backup

08
Phase 8: Dry Run

HARD GATE: Must succeed.

09
Phase 9: Execute Upgrade

Wait for all nodes to show new version (`kubectl get nodes`). If no progress after 20 min, investigate with `talosctl dmesg` and `kubectl describe nodes`.

10
Phase 10: Post-Upgrade Validation

Re-run Phase 6 health checks plus `kubectl version` and `kubectl get nodes -o wide`. Confirm all nodes report new version.

11
Phase 11: Roll Stale Secret Volume Mounts

K8s upgrades restart all kubelets. After restart, kubelet's `Watch`-based secret manager fails to re-establish watches for pre-existing pods' volume mounts. Secrets mounted as volumes become frozen at the pre-upgrade state. Detection: For every Running pod with a secret volume (non-subPath), exec `stat -c %Y <mount>/..data` and compare against the kubelet restart time. If the `..data` symlink timestamp predates the kubelet restart, the mount is stale.

12
Phase 12: Update Files & Report

Update `kubernetesVersion` in `talos/talconfig.yaml` Search for all old version references: Grep tool: search `<old-version>` (no `v` prefix) in `talos/*.yaml`, `docs/*.md`, `cluster/*.yaml` Grep may miss hookify-blocked files. Fallback: `grep -r "v<old-version>" cluster/ --include="*.yaml" -l 2>/dev/null`. Files found only by bash need `sed -i` instead of Edit tool. Common locations: `talos/talconfig.yaml`, `talos/README.md`, `cluster/flux/meta/cluster-settings.yaml`, `kubernetes-json-schema` URLs in 30+ manifest files

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.