What problem does it solve?
Kubernetes Gateway API upgrades often fail in subtle ways because controllers and CRDs evolve across alpha, beta, and GA, causing inconsistent watch/CRUD behavior or broken compatibility.
Core Features & Use Cases
- API version lifecycle strategy: Guidance for upgrading Gateway API and related Kubernetes resources across alpha → beta → GA while preserving compatibility guarantees.
- Controller-side upgrade tactics: Techniques for version probing, safe fallback, and consistent version selection across watch, preflight, CRUD, and status writes.
- Canonical internal typing: Methods to unify version-specific inputs into a single internal model so business logic does not fork per API version.
- Non-Kubernetes input normalization: A parsing-first conversion flow for filesystem/static sources when API Server conversion is unavailable.
- Practical case studies & test matrix: Concrete examples (ReferenceGrant, BackendTLSPolicy, TLSRoute) plus a minimum test checklist to validate correctness.
Quick Start
Use this skill to plan and implement a single-version-probe plus canonical-type upgrade approach for your Edgion controller when migrating Gateway API resources across versions.