k8s-yaml-convert

Convert Kubernetes manifests into AKS-ready YAML with migration annotations.

1|Updated Mar 20, 2026

Search Tags:#automation #migration #kubernetes #yaml #manifests #aks

Ready to run

npx skills add https://github.com/Dongbumlee/container-migration-copilot --skill k8s-yaml-convert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: k8s-yaml-convert
Source: https://github.com/Dongbumlee/container-migration-copilot/tree/main/.github/plugins/container-migration/skills/k8s-yaml-convert
Command: npx skills add https://github.com/Dongbumlee/container-migration-copilot --skill k8s-yaml-convert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating Kubernetes workloads to AKS often requires manual rewriting of manifests to align with AKS API versions, storage classes, ingress controllers, identity bindings, and platform annotations. This skill automates the initial pass of that conversion while preserving semantics.

Core Features & Use Cases

API version updates and compatibility checks for deployments, services, ingress, and other resources.
StorageClass and CSI driver translation to AKS-native equivalents.
Ingress and load-balancer annotation transformations for AKS hosting and traffic routing.
Automated migration annotations and traceability for audit and rollback.
Use Case: Dev teams migrating a Kubernetes namespace to AKS can generate a consistent, Azure-ready manifest set for review.

Quick Start

Provide the source Kubernetes manifests and the migration design decisions to generate AKS-ready YAML with migration annotations.

Frequently Asked Questions about k8s-yaml-convert

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

FAQPage Schema

How do I convert Kubernetes manifests to AKS-ready YAML automatically?▼

To convert Kubernetes manifests to AKS-ready YAML, provide source manifests and migration decisions to automate API version updates, storage class mapping, ingress annotations, and RBAC adaptation while preserving workload semantics.

What Kubernetes resources are supported when migrating manifests to AKS?▼

Kubernetes manifest migration to AKS supports deployments, services, ingress, storage classes, and RBAC configurations, applying Azure-native mappings for API versions, CSI drivers, load-balancer annotations, and workload identity bindings.

Can I use this to update Kubernetes API versions and storage classes for AKS compatibility?▼

Yes, you can update Kubernetes API versions and translate storage classes to AKS-native CSI driver equivalents, ensuring source manifests meet AKS compatibility requirements across deployments, services, and ingress resources.

How does workload identity and RBAC adaptation work when converting manifests for AKS?▼

Workload identity and RBAC adaptation during AKS manifest conversion transforms source Kubernetes role bindings and identity configurations into Azure-native mappings, maintaining semantic equivalence while applying required AKS annotations.

Does converting Kubernetes manifests to AKS YAML preserve migration traceability for rollback?▼

Converting Kubernetes manifests to AKS YAML applies automated migration annotations that provide traceability for audit and rollback, ensuring each transformation step is documented within the generated manifests.

What's the best way to handle ingress and load-balancer annotations for AKS hosting?▼

The best way to handle ingress and load-balancer annotations for AKS hosting is automated transformation, which applies Azure-native traffic routing annotations to source Kubernetes manifests during the AKS YAML conversion process.