Add eks-version-upgrade-readiness custom transformation#72
Open
brunokktro wants to merge 5 commits into
Open
Conversation
Analyzes and transforms Kubernetes manifests, Helm charts, Kustomize overlays, Terraform, and CDK code for Amazon EKS version upgrade compatibility. Detects removed/deprecated APIs, updates apiVersions and resource fields, validates addon compatibility, and generates a migration report with manual action items and a sequential upgrade path. Complements the Upgrade Controller for Amazon EKS (cluster-side execution) by handling the code-side readiness.
- api-removals-by-version.md: Kubernetes API removal table (1.16-1.36) plus quick upgrade-path lookup - eks-specific-changes.md: EKS-specific changes per version and addon compatibility matrix - examples-before-after.md: 8 concrete before/after transformations
…oubleshooting, and Repository Structure - Replace internal GitLab tool references with public EKS upgrade docs (cluster upgrade best practices + EKS Upgrade Insights) - Add BENCHMARKS.md with end-to-end test results: 3 repositories (K8s manifests, Terraform, Helm) run via atx custom def exec, 14/14 detections, 13/13 transformations, all validators passing - Add Troubleshooting section (6 scenarios) - Add Repository Structure tree at the bottom of the README
kubectl apply --dry-run=server against a real EKS 1.35 control plane: 6/6 transformed resources accepted. Negative confirmation included: the flag-only PSP correctly fails (API removed), validating the design.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new community-sourced custom transformation for AWS Transform: EKS Version Upgrade Readiness.
Analyzes and transforms Kubernetes manifests, Helm charts, Kustomize overlays, Terraform, and AWS CDK code for compatibility with a target Amazon EKS/Kubernetes version. It detects removed/deprecated APIs, updates
apiVersionfields and resource structures, validates addon compatibility, and generates aMIGRATION_REPORT.mdwith manual action items and a documented sequential upgrade path.This complements (does not duplicate) cluster-upgrade orchestration tools — it focuses exclusively on the code that runs on the cluster, not the cluster upgrade execution itself.
What's included
Testing
jboss-to-springbootandkubernetes-readiness-migrationsamples in this directory.atx custom def execagainst a live customer repo — happy to iterate on structure/content based on maintainer feedback.Notes
community-sourced-transformations/.