Loading...

XML

Word

Printable

Proposed title of this feature request
Enhance upgrade path api to calculate the shortest upgrade path for indirect upgrades
What is the nature and description of the request?
Enhance the upgrade path calculation api to support generating the shortest upgrade path when there is no direct upgrade path available between two versions
Similar to the portal application:
https://access.redhat.com/labs/ocpupgradegraph/update_path / https://source.redhat.com/groups/public/atomicopenshift/atomicopenshift_blog/new_customer_portal_labs_app_openshift_container_platform_update_graph
Why does the customer need this? (List the business requirements here)
Customer development environment has more than 150 clusters
Having gained confidence with the OCP 4 upgrade process reliability - it is now a self service.
i.e. the project decided on the best time for upgrade (with down time as they don't have replicas in dev), triggering the upgrade through a web interface.
As of now there is no good option available to calculate the upgrade path in case there is no direct upgrade path between the source version and the target version.
List any affected packages or components.
api - adding new functionality which is not there yet