Jan Šafránek
Jan Šafránek
/approve storage parts
I am not sure about usage of the aggregated API server and "virtual resources" there - I can see it is possible to implement it this way, I just don't...
Not sure if it's needed, the feature was alpha in 1.25 and stays so in 1.26 /label lead-opted-in
I am linking all volume reconstruction PRs to this enhancement update - I am trying to make as small and independent PRs as possible.
> separate doc just for reconstruction in general That sounds good. Where the document should be? We still have https://github.com/kubernetes/community/tree/master/contributors/devel/sig-storage, but IMO it's not a good place.
IMO the first option makes more sense. Existing PVs should migrate silently to CSI and that's it. We should not add new features to in-tree volumes, even if they're migrated...
@zezaeoh do you know how it's possible that a volume for PV without `ClaimRef` is deleted? That should be nearly impossible.
I have a case where `started.json` is correct, but `finished.json` is empty. Is it the same bug? https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-csi-1-22-on-kubernetes-1-23/1559492392854228992