Closed davidvossel closed 1 year ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from davidvossel by writing /assign @davidvossel
in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
/cc @awels i'd be interested in what you think of this idea. It allows us to create a storageclass in the guest cluster without explicitly mapping to a specific infra storage class.
Is this for the 'regular' installation where the controller exists in tenant cluster? Or also for the 'split' configuration? I thought in the split configuration the tenant didn't know anything about the infra storage class already.
Is this for the 'regular' installation where the controller exists in tenant cluster? Or also for the 'split' configuration? I thought in the split configuration the tenant didn't know anything about the infra storage class already.
it would be used for either. the storageclass in the guest wouldn't specify an infra storageclass, and the csi controller would create a PVC without the storageclass as well, which would result in the default storageclass being used.
basically, defaults all the way down.
Okay I am slightly confused by the fact you say the tenant storage class, specifies the infra storage class to use. Only the controller should care about the infra storage class (so it can generate the DVs) I see no reasonable reason for the infra storage class to be passed as a parameter. It should be an argument to the controller when it is created.
But if we can start by eliminating one argument from the tenant storage class I am all for it.
/hold
I want to build of isaac's work here, https://github.com/kubevirt/csi-driver/pull/62, before merging this. We're working in similar areas and I think i can converge some of my work into his storageclass enforcement config options
obsoleted by https://github.com/kubevirt/csi-driver/pull/73
With the
useDefaultInfraStorageClass
parameter, a storageclass can be created in the guest cluster without having knowledge of what the underlying infra cluster provides. Whatever is the default storageclass on the infra will be used.