skills.rest
missBerg
missBergCOMMUNITY
Explore all skills by this author →
GitHub

eg-migrate

Automate Envoy Gateway version migrations with pre-flight checks and rollback guidance.

3|Updated Mar 8, 2026
Search Tags:#rollback#kubernetes#controller#upgrade#crd#migrate#envoy-gateway
One-click install
npx skills add https://github.com/missBerg/envoy-skills --skill eg-migrate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eg-migrate
Source: https://github.com/missBerg/envoy-skills/tree/main/gateway/adopters/skills/eg-migrate
Command: npx skills add https://github.com/missBerg/envoy-skills --skill eg-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate Envoy Gateway installations between versions with pre-flight checks, CRD upgrades, controller upgrade steps, and rollback guidance.

Core Features & Use Cases

  • Performs pre-flight validation of source and target versions, and creates a recovery backup
  • Applies CRD and controller upgrades in the correct sequence with rollback guidance
  • Verifies post-upgrade health and readiness across resources and workloads

Quick Start

Provide the From version and (optional) To version to start the migration workflow.

Frequently Asked Questions about eg-migrate

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

FAQPage Schema
How do I upgrade Envoy Gateway to a new version safely in Kubernetes?▼

Safe Envoy Gateway migration requires automating pre-flight checks, sequencing CRD and controller upgrades correctly, and verifying post-upgrade workload health to ensure a secure Kubernetes version transition.

What steps are required to migrate Envoy Gateway CRDs and controllers?▼

Migrating Envoy Gateway CRDs and controllers requires applying upgrades in a specific version-dependent sequence. The workflow includes validating source and target versions, backing up resources, updating CRDs, upgrading controllers, and checking workload readiness.

Do I need a backup before upgrading Envoy Gateway versions?▼

Yes, you need a validated backup of resources before upgrading Envoy Gateway versions. The migration workflow performs pre-flight validation of source and target versions and creates a recovery backup to ensure safe rollback if needed.

Can I rollback an Envoy Gateway upgrade if the migration fails?▼

Yes, you can rollback a failed Envoy Gateway upgrade. The migration workflow provides rollback guidance and creates a recovery backup during pre-flight checks, allowing you to revert CRD and controller upgrades if post-upgrade verification fails.

What tools are required to automate Envoy Gateway migration between versions?▼

Automating Envoy Gateway migration requires kubectl and helm tooling, along with access to target version artifacts like Helm charts or container images. These tools enable the sequenced CRD and controller upgrades within Kubernetes deployments.

Why does Envoy Gateway migration require version-specific sequencing?▼

Envoy Gateway migration requires version-specific sequencing because CRD schemas and controller compatibility change between releases. Applying upgrades in the correct order prevents resource conflicts and ensures workloads remain healthy throughout the transition.

Related Skills

Explore More Software Engineering Skills→
missBergmissBerg
3

aigw-contrib-e2e

Run end-to-end tests for Envoy Gateway and AI Gateway on Kubernetes clusters.

Community
Advanced
missBergmissBerg
3

eg-version

Identify Envoy Gateway versions and assess Gateway API upgrade readiness.

Community
Advanced
missBergmissBerg
3

eg-install

Generate a Helm install command for Envoy Gateway in Kubernetes and verify deployment.

Community
Advanced
onehouseinconehouseinc
19

clean-uninstall

Uninstalls the Quanton Operator Helm chart, secrets, and CRD from Kubernetes.

Official
Intermediate