Recording: https://youtu.be/1vdXQmGhreA
Attendees:
Agenda:
[agilboa] PR PVC spec mutating webhook rendering based on StorageProfiles
Eliminates the need for DVs for StorageProfile based rendering - auto-completion of PVC missing spec fields based on optimal values per StorageClass.
Complements CDI volume populators, as together they get DV pros without its cons.
Webhook intercepts only explicitly CDI-labeled PVCs, so it won't affect cluster stability if the CDI api server is down
What happens to labeled PVCs when the API server is down?
objectSelectors decide when to call out over HTTP to the webhook.
If there is a label, the request goes, and it fails.
And thus creation SHOULD fail. We should make sure this is the case
What happens to unlabeled PVCs when the API server is down?
Unlabeled PVCs are not affected at all
[mhenriks] not sure about this feature. At a minimum the webhook should be featuregated (not deployed otherwise) as well as label per pvc.
[agilboa] BZ The "snapshot" clone-strategy may not choose the correct VolumeSnapshotClass if there are multiple VSCs with the same driver
is it a real use case?
Currently looks for vsc.Driver == sc.Provisioner match
Proposed solution: add SnapshotClass field to StorageProfile spec - optional specific VolumeSnapshotClass name for CloneStrategySnapshot. If not set, a VolumeSnapshotClass is chosen according to the provisioner.