Change:
controllerRegistry registry.ControllerRegistry serviceRegistry    registry.ServiceRegistry minionRegistry     registry.MinionRegistry <del> // TODO: don't reuse non-threadsafe objects. random  *rand.Rand storage map[string]apiserver.RESTStorage </del> <ins> storage            map[string]apiserver.RESTStorage </ins> } // NewMemoryServer returns a new instance of Master backed with memory (not etcd).

Discussion:
We got CI failures across all CSI sidecars: ...... I see the following in all the failed jobs: Kubernetes e2e suite: [It] External Storage [Driver: ] [Testpattern: Dynamic PV (default fs)] provisioning should provision correct filesystem size when restoring snapshot to larger size pvc [Feature:VolumeSnapshotDataSource] expandless 46s { failed [FAILED] Filesystem resize failed when restoring from snapshot to PVC with larger size. Restored fs size: bytes is not larger than origin fs size: bytes. HINT: Your driver needs to check the volume in NodeStageVolume and resize fs if needed. HINT: For an example patch see: Expected <int: to be <int: In [It] at: @ 10/04/23 11:50:44.626 } The tests should pass. The failure shows up in the test-grid. No response_ <details</details<details</details<details</details<details</details<details</details<details</details
/sig storage
/triage accepted
CSI hostpath driver does not support expanding volume when creating PVC from VolumeSnapshot, so I expected the test should be skipped before getting to the point where it failed on L530.
These tests are creating a snapshot of a PVC and then creating another PVC from the snapshot with 1Gi more than original size and expect the restored size to be larger than original size. Sounds like something specific to hostpath.
After the creation of a snapshot from an existing PVC. A new PVC is resultant from this snapshot with a size that exceeds the original PVC by 1Gi. The expected result is that the restored PVC size should be larger than the original PVC. it is noted that this issue may be related to the hostpath storage type, suggesting that there might be a specific problem or unexpected behavior associated with hostpath storage may be possible.
I reproduced it in the test environment and found the same result, the size before and after the expansion is the same, the e2e detection logic seems to be useless for csi-driver-host-path, and it is reasonable to say that it should not be able to run the previous k8s version e2e as well. seems like it was changed 8 months ago. any ideas?

Can you update the deployment folder to match the new versions we are supporting now (1.26, 1.27, 1.28)? Make sure FSResizeFromSourceNotSupported is set to true for every version. See this PR:
okay~
This is not fixed yet. /reopen
Reopened this issue. <detailsIn response to : This is not fixed yet. Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Tests are still failing on sidecar repos. From the build logs: I don't see the new parameter in test- in v1.11.0: It's in the latest code: We need to cut a new csi-driver-host-path release and update image in in csi-release-tools.
I can help with updating the csi-release-tools after the new version is released~
csi-driver-host-path 1.12 is released: Can you help update the csi-release-tools? Thanks.
ptal~
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Still fails: Need to update images in test-infra:
Fixed now.