Check for newer fields when deciding expansion recovery feature status

[gnufied]

Fixes #131402

Apart from tests here, I have manually verified that this works as expected:

Before:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  annotations:
  finalizers:
  - kubernetes.io/pvc-protection
  name: csi-pvc
  namespace: vim1
  resourceVersion: "574"
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 4Gi
  storageClassName: csi-hostpath-sc
  volumeMode: Filesystem
  volumeName: pvc-7ba4e352-5b28-494c-b68b-c2fbaf9d6221
status:
  accessModes:
  - ReadWriteOnce
  allocatedResourceStatuses:
    storage: NodeResizePending
  allocatedResources:
    storage: 4Gi
  capacity:
    storage: 4Gi
  phase: Bound

After:

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  finalizers:
  - kubernetes.io/pvc-protection
  name: csi-pvc
  namespace: vim1
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 6Gi
  storageClassName: csi-hostpath-sc
  volumeMode: Filesystem
  volumeName: pvc-7ba4e352-5b28-494c-b68b-c2fbaf9d6221
status:
  accessModes:
  - ReadWriteOnce
  allocatedResourceStatuses:
    storage: NodeResizeInProgress
  allocatedResources:
    storage: 6Gi
  capacity:
    storage: 4Gi
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2025-04-23T20:03:23Z"
    status: "True"
    type: Resizing
  - lastProbeTime: null
    lastTransitionTime: "2025-04-23T20:03:23Z"
    message: Waiting for user to (re-)start a pod to finish file system resize of
      volume on node.
    status: "True"
    type: FileSystemResizePending
  phase: Bound
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  finalizers:
  - kubernetes.io/pvc-protection
  name: csi-pvc
  namespace: vim1
  resourceVersion: "763"
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 6Gi
  storageClassName: csi-hostpath-sc
  volumeMode: Filesystem
  volumeName: pvc-7ba4e352-5b28-494c-b68b-c2fbaf9d6221
status:
  accessModes:
  - ReadWriteOnce
  allocatedResources:
    storage: 6Gi
  capacity:
    storage: 6Gi
  phase: Bound

/sig storage

Check for newer resize fields when deciding recovery feature's status in kubelet

[k8s-ci-robot]

Please note that we're already in Test Freeze for the release-1.33 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.33.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Wed Apr 23 13:35:19 UTC 2025.

[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-sigs/prow repository.

[gnufied]

/kind bug

[gnufied]

/test pull-kubernetes-e2e-gce

[msau42]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 24ac1ef2fa6ead82e4d2153acef8440a18523fb5

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gnufied, msau42

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 [gnufied,msau42]

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

[pacoxu]

/test pull-kubernetes-e2e-gce