fix: Changes to users approving scripts

[jhutar]

Description

Changes to users approving scripts

How Has This Been Tested?

Was tested locally. Scripts are meant for manual usage only.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from jhutar. For more information see the Kubernetes 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:

• tests/load-tests/OWNERS

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

[jhutar]

/test ?

[openshift-ci]

@jhutar: The following commands are available to trigger required jobs:

• /test images
• /test load-test-ci-100u
• /test load-test-ci-10u
• /test load-test-ci-1u
• /test load-test-ci-50u
• /test load-test-ci-50u-realworld
• /test load-test-max-concurrency-realworld
• /test max-concurrency

The following commands are available to trigger optional jobs:

• /test redhat-appstudio-e2e

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-konflux-ci-e2e-tests-main-images

In response to this:

/test ?

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.

[jhutar]

/rerurn

[jhutar]

/test load-test-ci-100u

[jhutar]

Triggered /test load-test-ci-100u to test unrelated change of secrets in Vault that is supposed to fix periodic jobs.

[openshift-ci]

@jhutar: The following test 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/load-test-ci-100u	77c8410	link	true	/test load-test-ci-100u

Full PR test history. Your PR dashboard.

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.