kubelet: Fix fs quota monitoring on volumes

[alex-matei]

What type of PR is this?

Add one of the following kinds:
/kind bug

What this PR does / why we need it:

File system quota monitoring setup fails on subsequent invocations, each time quota setup is invoked a new random UID is generated for each pod and compared with the previously stored UID.
This PR fixes it by keeping track of mapping between internal uid generated for a pod and actual external pod uid.
If there is already a quota project id associated with the folder it uses that instead of returning an error.
If quota is already set on a folder and the quota is the same it does an early exit.

Which issue(s) this PR fixes:

Fixes #114506, #112081, #115309

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Hi @alex-matei. 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.

[pacoxu]

/cc

[pacoxu]

I tried to fix it at #112624.

• Have you tested your fix?

[alex-matei]

Hi @pacoxu, I tested the fix and it works, I modified AssignQuota to be idempotent.

[pacoxu]

/ok-to-test

[pacoxu]

/retest

[alex-matei]

Rebased on top of master to see if it fixes the failing tests.

Edit: I looked at the job history and it doesn't seem related, those tests failed continuously since December.

[jsafrane]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alex-matei, jsafrane

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:

• pkg/volume/OWNERS [jsafrane]

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

[pacoxu]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 0fe1ca01e09ff7fa3475a1c3c70221cae3bff01c

[pacoxu]

/retest-required
/skip

[k8s-ci-robot]

@alex-matei: 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
pull-kubernetes-node-kubelet-serial-crio-cgroupv1	b011f38559fb727e103474ec957178fbc12e59af	link	false	/test pull-kubernetes-node-kubelet-serial-crio-cgroupv1
pull-kubernetes-node-kubelet-serial-crio-cgroupv2	b011f38559fb727e103474ec957178fbc12e59af	link	false	/test pull-kubernetes-node-kubelet-serial-crio-cgroupv2
pull-kubernetes-unit	b225d6c	link	unknown	/test pull-kubernetes-unit
pull-kubernetes-e2e-gce	b225d6c	link	unknown	/test pull-kubernetes-e2e-gce

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[pacoxu]

/test pull-kubernetes-e2e-gce

[pacoxu]

/test pull-kubernetes-unit

[pacoxu]

Should this be cherry-picked to v1.26 and v1.25?

[alex-matei]

I think it would be useful.