-
Feature
-
Resolution: Done
-
Major
-
None
Feature Overview (aka. Goal Summary)
This feature introduces a new command oc adm upgrade recommend in Tech Preview that improves how cluster administrators evaluate and select version upgrades.
Goals (aka. expected user outcomes)
- Enable users (especially those with limited OpenShift expertise) to make the upgrade selection process easily.
- Reduce information overload
- Provide clear, actionable recommendations for next version
- Shows relevant warnings and risks per cluster
- Help customers make informed decisions about when to initiate upgrades
Requirements (aka. Acceptance Criteria):
- Allows targeting specific versions with --version
- Shows conditional update risks
- Shows only recent relevant releases instead of all versions
- Limited to 2 per release
- highlight the recommended version
- Shows upgrade blockers and risks
- Shows documentation/KCS links for more details about recommendation
- Shows grouping based on security/performance/features changes in versions
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
Deployment considerations | List applicable specific needs (N/A = not applicable) |
Self-managed, managed, or both | Self-managed |
Classic (standalone cluster) | standalone |
Hosted control planes | yes |
Multi node, Compact (three node), or Single node (SNO), or all | All |
Connected / Restricted Network | All |
Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | All |
Operator compatibility | |
Backport needed (list applicable versions) | |
UI need (e.g. OpenShift Console, dynamic plugin, OCM) | |
Other (please specify) |
Use Cases (Optional):
Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.
<your text here>
Questions to Answer (Optional):
Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.
<your text here>
Documentation Considerations
Add docs for recommend command
Interoperability Considerations
Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? Initial completion during Refinement status.
<your text here>
- clones
-
OCPSTRAT-1834 OCP Update Precheck command to improve update experience
- In Progress
- links to