Hide Forgot
Document URL: https://docs.openshift.com/container-platform/3.9/upgrading/automated_upgrades.html Section Number and Name: Upgrading Cluster (probably both automated and manual upgrade sections) Describe the issue: Engineering have suggested validate 3.7 storage migration the day before the upgrade using oc adm migrate storage --include=* --loglevel=2 This would ensure some potential problems can be spotted early and can be resolved before going into outage window for upgrade to 3.9. Suggestions for improvement: Include suggestion as per above.
This is a general suggestion applicable to all upgrades.
Work in progress: https://github.com/openshift/openshift-docs/pull/11484
BTW, it's a good idea to run this migration prior to all upgrades whether it's a 3.y.z to 3.y.z+1 upgrade or 3.y 3.y+1 upgrade. Lets add this to 3.9 and 3.10 docs too.
3.7: https://github.com/openshift/openshift-docs/pull/11484 3.9: https://github.com/openshift/openshift-docs/pull/11509 3.10+: https://github.com/openshift/openshift-docs/pull/11505
For all, it's better to add "--config /etc/origin/master/admin.kubeconfig" for the command. For pr 11484, seems no need to specify "3.7 ", refer to other two prs. For pr 11505, miss "--confirm" for the command and wrong version of "3.7".
Thanks! I made some updates. Please review.
LGTM
Thank you!
This content is now published: https://access.redhat.com/documentation/en-us/openshift_container_platform/3.10/html/upgrading_clusters/install-config-upgrading-automated-upgrades#upgrade-workflow