Cherry pick #106045 to 1.20: Fix concurrent map writes error in kube-apiserver

[chenlinx17]

What type of PR is this?

/kind bug

What this PR does / why we need it:

this PR #106045 adds a sync.mutex in auditHandler to protect map audit.Event.Annotations from concurrent writes

Which issue(s) this PR fixes:

Fixes a concurrent map writes bug when recording audit event in the delete-collection scenario

Special notes for your reviewer:

this bug trigger condition:
1、enabled audit log for kube-apiserver
2、enabled multi-goroutine for delete collection (--delete-collection-workers > 1)

Does this PR introduce a user-facing change?

NONE

[k8s-ci-robot]

@chenlinx17: This cherry pick PR is for a release branch and has not yet been approved by Release Managers.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved (/lgtm + /approve) by the relevant OWNERS.

AFTER it has been approved by code owners, please ping the kubernetes/release-managers team in a comment to request a cherry pick review.

(For details on the patch release process and schedule, see the Patch Releases page.)

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]

Hi @chenlinx17. 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.

[tanjing2020]

/ok-to-test

[chenlinx17]

/cc @tkashem @sttts

[tkashem]

/lgtm

[fedebongio]

/triage accepted

[chenlinx17]

/priority important-soon

[chenlinx17]

/cc @lavalamp @smarterclayton @sttts

[dims]

/approve @sttts @tkashem @liggitt

[sttts]

/approve

Checked again master PR.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chenlinx17, dims, sttts

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:

• staging/src/k8s.io/apiserver/OWNERS [sttts]

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

[puerco]

Thanks!
/lgtm

[puerco]

/test pull-kubernetes-e2e-gce-ubuntu-containerd

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest