Tesshu Flower

I'd like to add a +1 for this as well. Would it make sense to have something that can be configured in the Subscription along with these other settings? https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/subscription-config.md

@viju2008 Looking at the code that creates the service, I don't see why NodePort wouldn't work. Have you tried it out yourself in your environment? Wondering if just a doc...

/hold

Some more context - I was testing with the CSI HostPath driver and the information is also not present in the individual snapshots, as `spec.source.persistentVolumeClaimName` is not set. Example volumesnapshot...

> This works as designed as we don't want each individual snapshot to be dynamically created. Makes sense, thanks - I think it does mean I don't currently have any...

Thanks for this info @leonardoce and @xing-yang . In my case I'm not developing a CSI driver, but looking at it from an end-user perspective. I think this is workable,...

@dhess This is an interesting one. I'm not sure the workaround used for `Direct` mode will work, as it relies on finding another active pod that's currently using the PVC...

@dhess there's nothing specific in VolSync that you should need to do to ensure compatibility. I guess normally I'd expect that the first consumer (the volsync mover pod in this...

> 👋 this issue also happens with CSI democrati-csi local-hostpath using the volsync volumepopulator. > > [democratic-csi/democratic-csi#329](https://github.com/democratic-csi/democratic-csi/issues/329) > > seems to be a time based racecondition. @danielsand I don't think...

@dhess is your storageclass using a VolumeBindingMode of `WaitForFirstConsumer`? VolSync doesn't create the cache PVC until just before creating the job, so normally I think it should be figured out...