Volume resizing issue

[kon-angelo]

How to categorize this issue?

/area control-plane
/kind enhancement
/platform aws

What would you like to be added:

Disable RecoverVolumeExpansionFailure in the csi-resizer is not all workerpools are on v1.32 and above

Why is this needed:

On v1.32 RecoverVolumeExpansionFailure turned beta and enabled by default. This will add new fields in the PVC status during operations like during a resize. This works as a "single-flight" lock mechanism. This will prevent the resizer to do subsequent operations under certain conditions.

If you try to perform a live resize on a pod scheduled on v1.31 worker node on a v1.32 KAPI, there is a mismatch between the enablement of the FGs between the resizer and the kubelet. The resize requires the kubelet to successfully respond that the operation is completed but since the FG is not enabled for the v1.31 kubelet this will not happen. As a result the PVC status is populated always with a condition that prevents the resizer from subsequent operations.

[kon-angelo]

This is likely patched by kubernetes/kubernetes#131418. It requires a kubelet version of v1.31.9 or higher

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all issues.
This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 60d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 60d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as active with /lifecycle active
• Mark this issue as frozen with /lifecycle frozen
• Mark this issue as fresh with /remove-lifecycle stale
• Mark this issue as rotten with /lifecycle rotten
• Close this issue with /close

/lifecycle stale