Large secrets

[paigerube14]

Using kube burner to create 10 secrets per namespace

https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-65206

Based on Lena's script here: https://github.com/lenahorsley/svt/blob/9319303ce2becb9e76bf9c5aff4214893bdadfff/openshift_performance/ci/scripts/large_object_list/large_object_list.sh

https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/scale-ci/job/e2e-benchmarking-multibranch-pipeline/job/regression-test/403/console

[lenahorsley]

@paigerube14 I'm okay with this. I ran the test and saw the expected and actual secrets in the log.

12-05 11:20:57.389  time="2023-12-05 16:20:57" level=info msg="Verifying created objects"
12-05 11:20:58.314  time="2023-12-05 16:20:58" level=info msg="secrets found: 1000 Expected: 1000"
12-05 11:20:58.314  time="2023-12-05 16:20:58" level=info msg="Job large-secrets took 50.17 seconds"
12-05 11:20:58.314  time="2023-12-05 16:20:58" level=info msg="Finished execution with UUID: 21638035-f785-4892-

[lenahorsley]

/lgtm

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closed this PR.

In response to [this](https://github.com/openshift/svt/pull/770#issuecomment-2097686834): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[qiliRedHat]

@paigerube14 I realized this PR isn't merged when I tried to run https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-65206. So I reopened it.

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: paigerube14

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

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift/svt/blob/master/OWNERS)~~ [paigerube14] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[openshift-ci[bot]]

@paigerube14: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).