platform-gke

Map GKE concepts to AKS equivalents for Kubernetes migration planning.

1|Updated Mar 20, 2026

Search Tags:#migration #gcp #azure #kubernetes #cloud #aks #gke

Ready to run

npx skills add https://github.com/Dongbumlee/container-migration-copilot --skill platform-gke

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates migrating Kubernetes workloads from Google Kubernetes Engine (GKE) to Azure Kubernetes Service (AKS) by providing explicit concept-to-concept mappings and deployment guidance, reducing manual translation effort and errors during cloud platform migrations.

Core Features & Use Cases

GKE to AKS mapping tables for Identity & Access, Storage, Networking, Infrastructure as Code, Database & Service Connectivity, Autopilot considerations, Service Mesh, Observability, and Detection Signals.
Practical use cases: rehosting deployments, updating manifests, and aligning policies across GKE and AKS.
Guidance to plan migration with compatibility checks, resource and policy alignment, and risk mitigation.

Quick Start

Review your GKE manifests and map each concept to its AKS equivalent using the provided tables to begin the migration planning.

Frequently Asked Questions about platform-gke

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

FAQPage Schema

How do I map GKE concepts to AKS equivalents for a Kubernetes migration?▼

Migrating Kubernetes workloads from GKE to AKS requires explicit concept-to-concept mapping for Identity, Storage, Networking, and Infrastructure as Code to reduce manual translation effort and deployment errors during cloud platform transitions.

What is the best way to plan a GKE to AKS migration?▼

Planning a GKE to AKS migration requires reviewing existing Google Kubernetes Engine manifests, utilizing concept mapping tables for compatibility checks, and aligning Azure Kubernetes Service resources and policies to mitigate risks during workload rehosting.

Does this guidance cover GKE Autopilot and Service Mesh mappings for AKS?▼

Yes, the guidance covers GKE Autopilot considerations, Service Mesh, Observability, and Detection Signals, providing explicit mapping tables to streamline Kubernetes migrations and align policies across GKE and AKS environments.

How do I update Kubernetes manifests when rehosting from GCP to Azure?▼

Updating Kubernetes manifests when rehosting from GCP to Azure involves mapping Google Kubernetes Engine Database and Service Connectivity configurations to their Azure Kubernetes Service equivalents to ensure cross-cloud compatibility and successful workload deployment.

Can I use this mapping to align networking and access policies across GKE and AKS?▼

Yes, you can use the provided GKE to AKS mapping tables to align Identity, Access, and Networking policies across Google Kubernetes Engine and Azure Kubernetes Service, ensuring workload portability and cross-cloud compatibility during migration.