-
Notifications
You must be signed in to change notification settings - Fork 42.9k
Facilitate ConfigMap rollouts / management #22368
Copy link
Copy link
Open
Labels
area/app-lifecyclearea/configmap-apiarea/declarative-configurationpriority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.sig/appsCategorizes an issue or PR as relevant to SIG Apps.Categorizes an issue or PR as relevant to SIG Apps.sig/service-catalogCategorizes an issue or PR as relevant to SIG Service Catalog.Categorizes an issue or PR as relevant to SIG Service Catalog.
Description
Metadata
Metadata
Assignees
Labels
area/app-lifecyclearea/configmap-apiarea/declarative-configurationpriority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.sig/appsCategorizes an issue or PR as relevant to SIG Apps.Categorizes an issue or PR as relevant to SIG Apps.sig/service-catalogCategorizes an issue or PR as relevant to SIG Service Catalog.Categorizes an issue or PR as relevant to SIG Service Catalog.
Type
Projects
Status
Needs Triage
To do a rolling update of a ConfigMap, the user needs to create a new ConfigMap, update a Deployment to refer to it, and delete the old ConfigMap once no pods are using it. This is similar to the orchestration Deployment does for ReplicaSets.
One solution could be to add a ConfigMap template to Deployment and do the management there.
Another could be to support garbage collection of unused ConfigMaps, which is the hard part. That would be useful for Secrets and maybe other objects, also.
cc @kubernetes/sig-apps-feature-requests