Skip to content

[release-4.21] OCPBUGS-73808: update watch request limits for cluster-autoscaler-operator #30691

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
openshift-merge-bot merged 1 commit into from
Jan 15, 2026
Merged

[release-4.21] OCPBUGS-73808: update watch request limits for cluster-autoscaler-operator #30691

openshift-merge-bot merged 1 commit into from
Jan 15, 2026

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Jan 14, 2026

This is an automated cherry-pick of #30656

/assign elmiko

@elmiko
update watch request limits for cluster-autoscaler-operator
f53916b 
this change increases the limit on the vsphere platform. it is being
changed to account for an increase of watch requests on the vsphere
platform. the increase in requests in associated with the organic growth
of the kubernetes project and associated dependencies.
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jan 14, 2026
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 14, 2026

@openshift-cherrypick-robot: Jira Issue OCPBUGS-69676 has been cloned as Jira Issue OCPBUGS-73808. Will retitle bug to link to clone.
/retitle [release-4.21] OCPBUGS-73808: update watch request limits for cluster-autoscaler-operator

Details

In response to this:

This is an automated cherry-pick of #30656

/assign elmiko

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 openshift-ci bot changed the title [release-4.21] OCPBUGS-69676: update watch request limits for cluster-autoscaler-operator [release-4.21] OCPBUGS-73808: update watch request limits for cluster-autoscaler-operator Jan 14, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 14, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 14, 2026

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-73808, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #30656

/assign elmiko

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 openshift-ci bot requested review from deads2k and sjenning January 14, 2026 20:32
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2026

@openshift-cherrypick-robot: 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.

@elmiko
Copy link
Contributor

elmiko commented Jan 15, 2026

/lgtm
/verified by elmiko

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 15, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 15, 2026

@elmiko: This PR has been marked as verified by elmiko.

Details

In response to this:

/lgtm
/verified by elmiko

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 openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 15, 2026
@neisw
Copy link
Contributor

neisw commented Jan 15, 2026

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 15, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elmiko, neisw, openshift-cherrypick-robot

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@neisw
Copy link
Contributor

neisw commented Jan 15, 2026

/backport-risk-assessed

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 15, 2026
@neisw
Copy link
Contributor

neisw commented Jan 15, 2026

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 15, 2026
@neisw
Copy link
Contributor

neisw commented Jan 15, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 15, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 15, 2026

@neisw: This pull request references Jira Issue OCPBUGS-73808, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-69676 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-69676 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

Requesting review from QA contact:
/cc @prozehna

Details

In response to this:

/jira refresh

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 openshift-ci bot requested a review from prozehna January 15, 2026 17:30
@openshift-merge-bot openshift-merge-bot bot merged commit 2af81ff into openshift:release-4.21 Jan 15, 2026
8 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 15, 2026

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-73808
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-73808 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This is an automated cherry-pick of #30656

/assign elmiko

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-merge-robot
Copy link
Contributor

openshift-merge-robot commented Jan 17, 2026

Fix included in accepted release 4.21.0-0.nightly-2026-01-17-030111

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@deads2k deads2k Awaiting requested review from deads2k

@sjenning sjenning Awaiting requested review from sjenning

@prozehna prozehna Awaiting requested review from prozehna

Assignees

@dgoodwin dgoodwin

@elmiko elmiko

@adambkaplan adambkaplan

@kasturinarra kasturinarra

@Moebasim Moebasim

@jadhaj jadhaj

@lyman9966 lyman9966

@pamoedom pamoedom

@gangwgr gangwgr

@prabhapa prabhapa

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.