skills.rest
air-gapped
air-gappedOFFICIAL
Explore all skills by this author →
GitHub

rancher-upgrade

Plan and sequence community-edition Rancher upgrades across air-gapped multi-cluster fleets.

5|1|Updated Apr 19, 2026
Search Tags:#upgrade#downtime#cross-cluster#air-gap#rancher#KDM#backup-rollback
One-click install
npx skills add https://github.com/air-gapped/skills --skill rancher-upgrade
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rancher-upgrade
Source: https://github.com/air-gapped/skills/tree/main/.claude/skills/rancher-upgrade
Command: npx skills add https://github.com/air-gapped/skills --skill rancher-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan and sequence COMMUNITY-edition Rancher upgrades across air-gapped multi-cluster fleets — a management/"hosting" Rancher cluster plus the downstream RKE2/K3s clusters it provisions. Covers the community release model (2.11→2.14, community-vs-Prime cadence, EOL), the Kontainer Driver Metadata (KDM) downstream- Kubernetes support matrix that decides which downstream k8s minors each Rancher version can manage (and the stranding risk when a host-Rancher bump outruns its sub-clusters), cross-cluster upgrade ordering, the embedded-CAPI→Rancher-Turtles migration, Fleet coupling, cert-manager/Helm/backup prerequisites, backup- restore-operator + etcd rollback, and the air-gapped upgrade procedure (which images/charts/KDM to mirror). Community editions only; Prime-gated content is flagged and excluded. Companion to k8s-components-checker, which owns the management-cluster k8s compatibility verdict; this skill owns the upgrade methodology and downstream coordination.

Core Features & Use Cases

  • Cross-cluster upgrade planning and sequencing (management cluster first, downstream scheduling)
  • KDM compatibility awareness and fleet-wide coordination
  • Air-gap upgrade procedures with backup prerequisites and rollback considerations
  • Companion to k8s-components-checker for end-to-end upgrade methodology

Quick Start

Begin by validating your Rancher admin kubeconfig, backing up the management cluster (BRO + etcd snapshot), and following the per-minor runbook to guide the upgrade steps.

Frequently Asked Questions about rancher-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade Rancher in an air-gapped multi-cluster environment?▼

To upgrade Rancher in an air-gapped multi-cluster environment, you must mirror required images, charts, and KDM data locally. The process sequences the management cluster upgrade first, followed by downstream clusters, ensuring backup prerequisites are met.

What is the correct upgrade order for Rancher management and downstream clusters?▼

The correct Rancher upgrade order requires upgrading the management or hosting cluster first before scheduling downstream RKE2/K3s cluster upgrades. This cross-cluster sequencing prevents compatibility stranding and ensures safe, auditable execution across the fleet.

How does KDM affect Rancher downstream Kubernetes compatibility during an upgrade?▼

KDM (Kontainer Driver Metadata) dictates which downstream Kubernetes minor versions each Rancher version can manage. Checking KDM during a Rancher upgrade prevents stranding risk, ensuring the host-Rancher bump does not outrun its managed sub-clusters.

Can I use this Rancher upgrade methodology for Prime editions?▼

No, this upgrade methodology explicitly covers community-edition Rancher deployments only, tracking the community release cadence and EOL. Prime-gated content is actively flagged and excluded from the cross-cluster upgrade runbooks and procedures.

What backup and rollback prerequisites are required before upgrading Rancher?▼

Before upgrading Rancher, you must complete prerequisites including backing up the management cluster using backup-restore-operator and etcd snapshots. These rollback prerequisites ensure you can safely recover the fleet if the upgrade execution encounters critical failures.

Why do I need to validate cert-manager and Helm versions before a Rancher upgrade?▼

Validating cert-manager and Helm versions is a mandatory pre-flight prerequisite for a Rancher upgrade because incompatible dependencies can cause downtime. Grounding steps in per-minor runbooks ensures all fleet coupling and embedded-CAPI migrations execute safely.

Related Skills

Explore More Software Engineering Skills→
phuetzphuetz
30

kubernetes

Consolidate kubectl, Helm, and ArgoCD workflows for Kubernetes cluster administration.

Community
Advanced
kettleofketchupkettleofketchup

calico

Deploy, configure, and troubleshoot Calico for Kubernetes cluster networking.

Community
Advanced
air-gappedair-gapped
5

k8s-components-checker

Survey Kubernetes clusters against an embedded compatibility registry for upgrade-readiness verdicts.

Official
Advanced
aws-samplesaws-samples
6

fsi-cyber-resilience

Implement cyber resilience with air-gapped backup and automated network isolation for core-banking workloads.

Official
Advanced