Skip to content

updated the memory resource for tekton resources to prevent OOMKills #6436

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

This PR increases the memory resource limits for the following components to reduce OOM-related instability:

  • pipeline-metrics-exporter
    
     Was occasionally consuming its full 6 GiB allocation, leading to instability.
    
      Increased memory limits to improve reliability and prevent potential OOM issues.
    
  • tekton-pipeline-remote-resolver
    
      Also observed to use up its full 8 GiB memory allocation intermittently.
    
      Increased memory limits to improve reliability and prevent potential OOM issues.
    

… pipeline-metrics-exporter

Signed-off-by: Abhishek Ghosh <[email protected]>
@openshift-ci openshift-ci bot requested review from enarha and ramessesii2 May 26, 2025 09:52
Copy link

openshift-ci bot commented May 26, 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

Copy link

openshift-ci bot commented May 26, 2025

Hi @ab-ghosh. Thanks for your PR.

I'm waiting for a redhat-appstudio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@enarha
Copy link
Contributor

enarha commented May 26, 2025

/ok-to-test

@aThorp96
Copy link
Contributor

/ok-to-test

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.

3 participants