[release-4.21] OCPBUGS-77647: remove resource limits from Agent CAPI provider by openshift-cherrypick-robot · Pull Request #7844 · openshift/hypershift

openshift-cherrypick-robot · 2026-03-03T08:55:58Z

This is an automated cherry-pick of #7812

/assign celebdor

/cherrypick release-4.20 release-4.19 release-4.18 release-4.17

The Agent CAPI provider deployment had resource limits (cpu: 200m, memory: 100Mi) that were copy-pasted from the upstream cluster-api-provider-agent operator-sdk scaffold defaults when the deployment was first added to HyperShift (commit 4a4630f, 2021-12-30). These limits were never intentionally sized for the workload. All other platforms (AWS, KubeVirt, PowerVS, GCP, Azure) only set resource requests without limits. Removing the limits aligns the Agent platform with this established convention and prevents unnecessary CPU throttling and OOM kills. Ref: OCPBUGS-76977 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

openshift-ci-robot · 2026-03-03T08:56:10Z

@openshift-cherrypick-robot: Jira Issue OCPBUGS-76997 has been cloned as Jira Issue OCPBUGS-77647. Will retitle bug to link to clone.
/retitle [release-4.21] OCPBUGS-77647: remove resource limits from Agent CAPI provider

Details

In response to this:

This is an automated cherry-pick of #7812

/assign celebdor

/cherrypick release-4.20 release-4.19 release-4.18 release-4.17

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.

coderabbitai · 2026-03-03T08:56:12Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

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

openshift-ci-robot · 2026-03-03T08:56:37Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-77647, 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.
expected dependent Jira Issue OCPBUGS-76997 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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 #7812

/assign celebdor

/cherrypick release-4.20 release-4.19 release-4.18 release-4.17

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.

celebdor · 2026-03-11T09:46:31Z

/jira refresh

openshift-ci-robot · 2026-03-11T09:46:36Z

@celebdor: This pull request references Jira Issue OCPBUGS-77647, 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.
expected dependent Jira Issue OCPBUGS-76997 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

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.

celebdor · 2026-03-11T09:50:20Z

/jira refresh

openshift-ci-robot · 2026-03-11T09:50:27Z

@celebdor: This pull request references Jira Issue OCPBUGS-77647, which is invalid:

expected dependent Jira Issue OCPBUGS-76997 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

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.

celebdor · 2026-03-11T09:52:25Z

/jira refresh
/retest-required

openshift-ci-robot · 2026-03-11T09:52:32Z

@celebdor: This pull request references Jira Issue OCPBUGS-77647, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.21.z) matches configured target version for branch (4.21.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-76997 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-76997 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (vkolodny@redhat.com), skipping review request.

Details

In response to this:

/jira refresh
/retest-required

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.

enxebre · 2026-03-11T10:15:43Z

/approve
/lgtm

openshift-ci · 2026-03-11T10:16:46Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre, 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:

~~OWNERS~~ [enxebre]

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

zhfeng · 2026-03-12T01:18:21Z

/retest

zhfeng · 2026-03-12T16:03:24Z

/verified by zhfeng

https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-hypershift-release-4.21-periodics-mce-e2e-agent-connected-ovn-ipv4-metal-conformance/2032036788041682944

openshift-ci-robot · 2026-03-12T16:37:08Z

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

Details

In response to this:

/verified by zhfeng

https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-hypershift-release-4.21-periodics-mce-e2e-agent-connected-ovn-ipv4-metal-conformance/2032036788041682944

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 · 2026-03-12T20:13:34Z

@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.

openshift-ci-robot · 2026-03-12T20:18:37Z

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-77647
✔️ 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-77647 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 #7812

/assign celebdor

/cherrypick release-4.20 release-4.19 release-4.18 release-4.17

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-cherrypick-robot · 2026-03-12T20:19:56Z

@openshift-cherrypick-robot: new pull request created: #7947

Details

In response to this:

This is an automated cherry-pick of #7812

/assign celebdor

/cherrypick release-4.20 release-4.19 release-4.18 release-4.17

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.

openshift-merge-robot · 2026-03-16T16:01:26Z

Fix included in accepted release 4.21.0-0.nightly-2026-03-16-041356

openshift-cherrypick-robot assigned celebdor Mar 3, 2026

openshift-cherrypick-robot mentioned this pull request Mar 3, 2026

OCPBUGS-76997: remove resource limits from Agent CAPI provider #7812

Merged

4 tasks

openshift-ci bot added the do-not-merge/needs-area label Mar 3, 2026

openshift-ci bot changed the title ~~[release-4.21] OCPBUGS-76997: remove resource limits from Agent CAPI provider~~ [release-4.21] OCPBUGS-77647: remove resource limits from Agent CAPI provider Mar 3, 2026

celebdor added the area/hypershift-operator Indicates the PR includes changes for the hypershift operator and API - outside an OCP release label Mar 3, 2026

openshift-ci bot removed the do-not-merge/needs-area label Mar 3, 2026

openshift-ci bot requested review from enxebre and muraee March 3, 2026 08:58

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 Mar 11, 2026

enxebre added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 11, 2026

openshift-ci bot assigned enxebre Mar 11, 2026

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 11, 2026

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 11, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 12, 2026

openshift-merge-bot bot merged commit 7ab6453 into openshift:release-4.21 Mar 12, 2026
17 checks passed

openshift-cherrypick-robot mentioned this pull request Mar 12, 2026

[release-4.20] OCPBUGS-78400: remove resource limits from Agent CAPI provider #7947

Open

Conversation

openshift-cherrypick-robot commented Mar 3, 2026

Uh oh!

openshift-ci-robot commented Mar 3, 2026

Uh oh!

coderabbitai bot commented Mar 3, 2026

Review skipped

Uh oh!

openshift-ci-robot commented Mar 3, 2026

Uh oh!

celebdor commented Mar 11, 2026

Uh oh!

openshift-ci-robot commented Mar 11, 2026

Uh oh!

celebdor commented Mar 11, 2026

Uh oh!

openshift-ci-robot commented Mar 11, 2026

Uh oh!

celebdor commented Mar 11, 2026

Uh oh!

openshift-ci-robot commented Mar 11, 2026

Uh oh!

enxebre commented Mar 11, 2026

Uh oh!

openshift-ci bot commented Mar 11, 2026

Uh oh!

zhfeng commented Mar 12, 2026

Uh oh!

zhfeng commented Mar 12, 2026

Uh oh!

openshift-ci-robot commented Mar 12, 2026

Uh oh!

openshift-ci bot commented Mar 12, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Mar 12, 2026

Uh oh!

openshift-cherrypick-robot commented Mar 12, 2026

Uh oh!

openshift-merge-robot commented Mar 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants