Support updating configmap

[msau42]

Migrating from kubernetes-retired/external-storage#1011
/kind feature

[cofyc]

I was asked several times by users why they applied new yaml files but provisioner cannot discover for new storage classes.
If no one is looking at it, I'll take it.
/assign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[msau42]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[bcollard]

Hello,

Yes, there is the configMap update but also another point: the daemonset must have every storageclass hostDir mounted on its pods so that it can discover new mounted sub-directories. So I suggest to guide people to use Kustomize + patches, so that for each update of the CM, the DaemonSet is notified and updated with a new CM name and with new volumeMounting (not sure if it's feasible).
This would need a step-by-step guide.

[bcollard]

/remove-lifecycle stale

[bcollard]

Please, what's your opinion about this?
My feeling is that most people need to deploy new apps regularly. So we cannot offer a static configuration through this configMap / DaemonSet combo.

What's the proposed way of working when one want to deploy a new app requiring some PV(s)?
How to update the DS and CM properly?