eg-version

Identify Envoy Gateway versions and assess Gateway API upgrade readiness.

3|Updated Mar 8, 2026

Search Tags:#kubectl #gateway-api #version-check #upgrade-readiness #envoy-gateway #crd-versions

Ready to run

npx skills add https://github.com/missBerg/envoy-skills --skill eg-version

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eg-version
Source: https://github.com/missBerg/envoy-skills/tree/main/gateway/adopters/skills/eg-version
Command: npx skills add https://github.com/missBerg/envoy-skills --skill eg-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify the Envoy Gateway version, verify compatibility with Gateway API versions and Kubernetes, and assess upgrade readiness to plan safe updates across clusters.

Core Features & Use Cases

Version discovery: read installed controller image, Helm app_version, and Gateway API CRD versions.
Compatibility assessment: review the compatibility matrix and note End-of-Life statuses.
Upgrade planning: provide guidance and checks to prepare for upgrades.

Quick Start

Run this to check your Envoy Gateway versions and upgrade readiness across your cluster.

Frequently Asked Questions about eg-version

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

FAQPage Schema

How do I check the installed Envoy Gateway version in my Kubernetes cluster?▼

To check the installed Envoy Gateway version, read the controller deployment image, Helm app_version, and Gateway API CRD statuses across your cluster to surface accurate version guidance.

How do I verify Envoy Gateway compatibility with Gateway API and Kubernetes versions?▼

Verify Envoy Gateway compatibility by reviewing the compatibility matrix against your detected Gateway API CRD versions and Kubernetes environment to note any End-of-Life statuses.

How do I assess upgrade readiness for Envoy Gateway across multiple releases?▼

Assess Envoy Gateway upgrade readiness by checking CRD and Helm-based upgrade paths, reviewing version statuses, and applying provided guidance to prepare for safe cluster updates.

Does this version check apply to Helm-based Envoy Gateway deployments?▼

Yes, this version check applies to Helm-based deployments by reading the Helm app_version alongside controller deployment images and CRD statuses to evaluate upgrade paths.

How do I plan a safe Envoy Gateway update using CRD version statuses?▼

Plan a safe Envoy Gateway update by reading CRD version statuses and Helm app_versions, then applying the generated compatibility and upgrade considerations to prepare your cluster.

What is the best way to identify End-of-Life statuses for Envoy Gateway components?▼

The best way to identify End-of-Life statuses is to review the compatibility matrix using discovered controller image versions and Gateway API CRD versions within your cluster environment.