Automated cherry pick of #120101: fix: concurrent map writes in e2e test

[dzjiang91]

Cherry pick of #120101 on release-1.28.

#120101: fix: concurrent map writes in e2e test

For details on the cherry pick process, see the cherry pick requests page.

NONE

[k8s-ci-robot]

Welcome @dzjiang91!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @dzjiang91. Thanks for your PR.

I'm waiting for a kubernetes 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/test-infra repository.

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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/test-infra repository.

[pohly]

/lgtm
/approve
/release-note-none
/kind cleanup
/cc kubernetes/release-managers

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 35960b21b64dd45fb8e70bda1f10b34faa8934d3

[liggitt]

/ok-to-test

[liggitt]

/retest

[xmudrii]

@dzjiang91 @pohly @liggitt Just to double check, is this affecting only v1.28 and v1.27?

[liggitt]

I don't know, but it's a test-only change, so it seems fine to improve 1.28 and 1.27 now and pick back further independently if needed

[xmudrii]

/release-note-edit

NONE

[xmudrii]

For RelEng:
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dzjiang91, pohly, xmudrii

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:

• test/e2e/storage/OWNERS [pohly]

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