Skip to content

CMP-3857: Add prerelease e2e test for operator memory with many namespaces - #1126

Closed
xiaojiey wants to merge 1 commit into
ComplianceAsCode:masterfrom
xiaojiey:OOM-check
Closed

xiaojiey wants to merge 1 commit into
ComplianceAsCode:masterfrom
xiaojiey:OOM-check

Conversation

@xiaojiey

@xiaojiey xiaojiey commented Mar 27, 2026 •

Copy link
Copy Markdown
Collaborator

This test verifies that the compliance operator does not experience excessive memory growth when there are many namespaces in the cluster.

The test creates 600 namespaces with network policies, runs a compliance scan, and measures memory usage before and after. It ensures that memory increase stays under 60Mi threshold to prevent OOM issues.

Test coverage:

  • Operator memory stability with 600+ namespaces
  • Proper handling of namespace scaling
  • Prevention of OOMKilled status under stress

--- PASS: TestOperatorMemoryWithManyNamespaces (292.11s)

@openshift-ci
openshift-ci Bot requested review from rhmdnd and yuumasato March 27, 2026 11:27
@openshift-ci

openshift-ci Bot commented Mar 27, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xiaojiey

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

@github-actions

Copy link
Copy Markdown

🤖 To deploy this PR, run the following command:

make catalog-deploy CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:1126-357513f2661896a8e444b2c6170d3452276bb149

@xiaojiey xiaojiey changed the title Add prerelease e2e test for operator memory with many namespaces CMP-3857: Add prerelease e2e test for operator memory with many namespaces Mar 27, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Collaborator

@xiaojiey: This pull request references CMP-3857 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 the "4.22.0" version, but no target version was set.

Details

In response to this:

This test verifies that the compliance operator does not experience excessive memory growth when there are many namespaces in the cluster.

The test creates 600 namespaces with network policies, runs a compliance scan, and measures memory usage before and after. It ensures that memory increase stays under 60Mi threshold to prevent OOM issues.

Test coverage:

  • Operator memory stability with 600+ namespaces
  • Proper handling of namespace scaling
  • Prevention of OOMKilled status under stress

--- PASS: TestOperatorMemoryWithManyNamespaces (292.11s)

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.

This test verifies that the compliance operator does not experience
excessive memory growth when there are many namespaces in the cluster.

The test creates 600 namespaces with network policies, runs a compliance
scan, and measures memory usage before and after. It ensures that memory
increase stays under 30Mi threshold to prevent OOM issues.

Test coverage:
- Operator memory stability with 600+ namespaces
- Proper handling of namespace scaling
- Prevention of OOMKilled status under stress
@github-actions

Copy link
Copy Markdown

🤖 To deploy this PR, run the following command:

make catalog-deploy CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:1126-dab556703d550cb231635d78ba6be4246cc794b6

@openshift-ci

openshift-ci Bot commented Apr 1, 2026

Copy link
Copy Markdown

PR needs rebase.

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.

@taimurhafeez

taimurhafeez commented Apr 20, 2026 •

Copy link
Copy Markdown
Collaborator

I have branched it out and rebased with master here.

@openshift-ci

openshift-ci Bot commented Jun 25, 2026

Copy link
Copy Markdown

@xiaojiey: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-config dab5567 link true /test e2e-aws-config
ci/prow/e2e-aws-scan-config dab5567 link true /test e2e-aws-scan-config
ci/prow/e2e-aws-serial dab5567 link true /test e2e-aws-serial
ci/prow/e2e-rosa dab5567 link true /test e2e-rosa
ci/prow/e2e-aws-serial-arm dab5567 link true /test e2e-aws-serial-arm
ci/prow/e2e-aws-deployment dab5567 link true /test e2e-aws-deployment
ci/prow/e2e-aws-parallel dab5567 link true /test e2e-aws-parallel
ci/prow/e2e-aws-parallel-arm dab5567 link true /test e2e-aws-parallel-arm

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

openshift-ci Bot commented Jul 26, 2026

Copy link
Copy Markdown

Stale PRs are closed after 21d of inactivity.

If this PR is still relevant, comment to refresh it or remove the stale label.
Mark the PR as fresh by commenting /remove-lifecycle stale.

If this PR is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci

openshift-ci Bot commented Aug 9, 2026

Copy link
Copy Markdown

Stale PRs rot after 14d of inactivity.

Mark the PR as fresh by commenting /remove-lifecycle rotten.
Rotten PRs close after an additional 7d of inactivity.

If this PR is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci

openshift-ci Bot commented Aug 16, 2026

Copy link
Copy Markdown

Rotten PRs close after 7d of inactivity.

Reopen the PR by commenting /reopen.
Mark the PR as fresh by commenting /remove-lifecycle rotten.

/close

@openshift-ci openshift-ci Bot closed this Aug 16, 2026
@openshift-ci

openshift-ci Bot commented Aug 16, 2026

Copy link
Copy Markdown

@openshift-ci[bot]: Closed this PR.

Details

In response to this:

Rotten PRs close after 7d of inactivity.

Reopen the PR by commenting /reopen.
Mark the PR as fresh by commenting /remove-lifecycle rotten.

/close

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.

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