Set minimum version of 4.20 required to upgrade to 4.21

[ngopalak-redhat]

Fixes: #OCPNODE-3722
This change introduces a gate to block 4.20 clusters from upgrading to 4.21 until the prerequisite patch for Auto Node Sizing has been applied.

Context: Clusters created before 4.21 must have Auto Node Sizing disabled by default.

Requirement: The necessary 4.20 patch openshift/machine-config-operator#5387 introduces a specific MachineConfig to enforce this disabled state.

Goal: This PR ensures upgrade safety by confirming the presence of that MachineConfig before proceeding to 4.21.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

@ngopalak-redhat: This pull request references OCPNODE-3722 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20.z" instead.

Details

In response to this:

Fixes: #OCPNODE-3722
This change introduces a gate to block 4.20 clusters from upgrading to 4.21 until the prerequisite patch for Auto Node Sizing has been applied.

Context: Clusters created before 4.21 must have Auto Node Sizing disabled by default.

Requirement: The necessary 4.20 patch openshift/machine-config-operator#5387 introduces a specific MachineConfig to enforce this disabled state.

Goal: This PR ensures upgrade safety by confirming the presence of that MachineConfig before proceeding to 4.21.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@ngopalak-redhat: This pull request references OCPNODE-3722 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20.z" instead.

Details

In response to this:

Fixes: #OCPNODE-3722
This change introduces a gate to block 4.20 clusters from upgrading to 4.21 until the prerequisite patch for Auto Node Sizing has been applied.

Context: Clusters created before 4.21 must have Auto Node Sizing disabled by default.

Requirement: The necessary 4.20 patch openshift/machine-config-operator#5387 introduces a specific MachineConfig to enforce this disabled state.

Goal: This PR ensures upgrade safety by confirming the presence of that MachineConfig before proceeding to 4.21.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[ngopalak-redhat]

/hold Until openshift/machine-config-operator#5387 is merged

[ngopalak-redhat]

@haircommander @sairameshv please review. I have kept it on hold so that 4.20 PR can be merged

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ngopalak-redhat]

/hold cancel

[ngopalak-redhat]

cc: @haircommander @sairameshv

[ngopalak-redhat]

/hold Wait will 4.20.5 build is made.

[ngopalak-redhat]

@wking and @sairameshv Can you review and remove hold on this PR? Updated the version number to 4.20.6 https://amd64.ocp.releases.ci.openshift.org/releasestream/4-stable/release/4.20.6

[sairameshv]

/lgtm
/hold cancel

[openshift-ci]

@ngopalak-redhat: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[sdodson]

/retitle Set minimum version of 4.20 required to upgrade to 4.21

[openshift-ci-robot]

@ngopalak-redhat: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

Fixes: #OCPNODE-3722
This change introduces a gate to block 4.20 clusters from upgrading to 4.21 until the prerequisite patch for Auto Node Sizing has been applied.

Context: Clusters created before 4.21 must have Auto Node Sizing disabled by default.

Requirement: The necessary 4.20 patch openshift/machine-config-operator#5387 introduces a specific MachineConfig to enforce this disabled state.

Goal: This PR ensures upgrade safety by confirming the presence of that MachineConfig before proceeding to 4.21.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[sdodson]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ngopalak-redhat, sairameshv, sdodson
Once this PR has been reviewed and has the lgtm label, please assign hongkailiu for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• build-suggestions/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment