harvester-upgrade

Plan and execute serial Harvester upgrades from 1.5.x to 1.8.x.

5|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/air-gapped/skills --skill harvester-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harvester-upgrade
Source: https://github.com/air-gapped/skills/tree/main/.claude/skills/harvester-upgrade
Command: npx skills add https://github.com/air-gapped/skills --skill harvester-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Upgrading Harvester clusters across air-gapped environments is risky without coordinated planning, gating, and a documented rollback strategy.

Core Features & Use Cases

  • Serial, no-skip upgrade ladder (1.5.x → 1.6.x → 1.7.x → 1.8.x) with per-hop gates and preventative checks
  • External Rancher coupling rules, UI extension sequencing, and per-hop runbooks to align all moving parts
  • Safety nets (restoreVM, PodDisruptionBudgets, pre-flight gates, and outage-free upgrade design) for guest clusters
  • Use cases: operators upgrading Harvester clusters in production or air-gapped labs while preserving guest workloads

Quick Start

Follow the per-hop runbook to execute a controlled, one-host-at-a-time Harvester upgrade.

Frequently Asked Questions about harvester-upgrade

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

FAQPage Schema
How do I safely upgrade Harvester clusters in an air-gapped environment?

The upgrade process uses a serial, no-skip ladder from 1.5.x to 1.8.x. It coordinates Rancher coupling, UI extension sequencing, and per-hop runbooks to guarantee one-host-at-a-time upgrades with pre-flight gates.

What is the safe upgrade path for migrating Harvester from version 1.5.x?

The safe upgrade path is a serial, no-skip ladder moving from 1.5.x to 1.6.x, 1.7.x, and finally 1.8.x. Each hop enforces preventative checks and per-hop gates to ensure cluster stability.

Can I upgrade Harvester without causing downtime for guest workloads?

Yes, you can upgrade Harvester without guest downtime by enforcing safety nets like restoreVM, PodDisruptionBudgets, and pre-flight gates. The process uses an outage-free, one-host-at-a-time upgrade design.

Do I need to coordinate Rancher UI extensions when upgrading Harvester?

Yes, you need to coordinate Rancher UI extensions when upgrading Harvester. The process enforces external Rancher coupling rules and UI extension sequencing to align all moving parts during the upgrade.

What safety nets are available if a Harvester upgrade gate fails?

Available safety nets include restoreVM, PodDisruptionBudgets, and pre-flight gates. These detect gate failures and guide operators through controlled rollback procedures to protect guest clusters.