[PLT-4667] Rewrite the EKS upgrade guide against the real 0.9.0 flow - #943
Open
iamjanr wants to merge 3 commits into
Open
[PLT-4667] Rewrite the EKS upgrade guide against the real 0.9.0 flow#943iamjanr wants to merge 3 commits into
iamjanr wants to merge 3 commits into
Conversation
…ions Requires mp_role_name for any cluster with MachinePool groups instead of relying on CAPA's dynamic per-nodegroup role; documents ownership for both create_iam values and adds a known-limitations table for MachinePool.
Realigns prerequisites, flags, and the MachineDeployment-to-MachinePool migration steps with the actual behavior of ecr_pull_through.py and upgrade-provisioner.py, and documents recovery steps for interrupted upgrades.
iamjanr
added
ai-assisted
wip
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.
PLT-4667 Rewrite the EKS upgrade guide against the real 0.9.0 flow
Description
upgrade.adoc(es/) rewritten against a real, live-validated 0.9.0 upgrade run (upgrade-provisioner.py,ecr_pull_through.py), instead of the previous 0.7.X→0.8.X-era description:0.9.Xscheme.helm_repositoryalready publishing the target cluster-operator chart.docker runexample (the image has noENTRYPOINT,python3 upgrade-provisioner.pymust be invoked explicitly).k8s_versionbump step documented in the main flow, expanded final verification (kubelet version per node,node_image-pinned group behavior).node_image-pinnedMachineDeploymentgroups do not get their Kubernetes version bumped either (same as legacy groups) — verified incluster-operator'skeoscluster_controller.go.mp_role_nameIAM role (vs. CAPA's per-nodegroup dynamic role), with the exactclusterawsadmprocedure for clusters that predate this requirement; manual node-group migration steps (the previous "guided migration" script was replaced, see the companion PLT-4265 PR); known MachinePool limitations table.Type of Change
Related Pull Requests
activate-capa-machinepool-features.pyandENIConfigauto-fix this guide documents.How Has This Been Tested?
Every command and claim in the rewritten sections was validated live against real test EKS clusters going through the actual 0.7.5→0.9.0 upgrade and MachinePool creation flow this session — not just proofread. Rendered with
asciidoctorafter each change (no warnings, all xrefs resolve).Checklist
ai-assistedat minimum.Additional Notes
en/translation not touched (repo convention: onlyes/is authored directly, translation team ports to English).