Skip to content

Follow-up: Apply Resource Limits for Tekton Components in Production #6874

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ab-ghosh
Copy link
Contributor

This PR mirrors the changes introduced in #6435 by applying CPU and memory limits for Tekton components in the production environments.

@openshift-ci openshift-ci bot requested review from ramessesii2 and Roming22 June 25, 2025 18:42
Copy link

openshift-ci bot commented Jun 25, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ab-ghosh
Once this PR has been reviewed and has the lgtm label, please assign roming22 for approval. For more information see the Code Review Process.

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

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

@aThorp96
Copy link
Contributor

/lgtm
/hold

We want to make sure we're monitoring this as it deploys. Because these are all new resource limits/requests, and since a misconfiguration here could cause the components to become unschedulable or be repeatedly evicted, let's target merging this during the maintenance window this Friday.

CC @enarha @hugares

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

Successfully merging this pull request may close these issues.

2 participants