k8s-analysis

Kubernetes manifests are analyzed for AKS migration readiness by parsing apiVersion and kind fields to detect platform-specific constructs, generating an analysis_report.md with a compatibility matrix and risk register.

Kubernetes manifest analysis for platform-specific constructs is the process of inventorying resources to detect signals from EKS, GKE, OpenShift, Rancher, Tanzu, and on-prem clusters to determine compatibility before moving to AKS.

Generate a migration readiness report by placing Kubernetes YAML manifests under migration/source/ and running the analysis, which produces an analysis_report.md containing evidence-based findings, a platform-detection summary, and a risk register.

Yes, you can detect EKS, GKE, OpenShift, Rancher, Tanzu, and on-prem cluster configurations by analyzing the manifests to identify platform-specific signals that affect AKS compatibility and rollout.

To run an AKS compatibility check, you need your Kubernetes YAML manifests placed under the migration/source/ directory, requiring no additional dependencies to generate the readiness analysis and executable plan.

A limitation when assessing Kubernetes manifests for AKS migration is that the analysis applies specifically to manifests located under migration/source/ during initial planning, focusing on parsed apiVersion and kind rather than runtime behavior.