Facilitate ConfigMap rollouts / management
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
Posted by bgrant0607 on Mar 2, 2016, 5:26 PM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
support (Sysadmin)
Support connecting to remote devcontainers (devcontainer on remote host)
Option to use Waffle menu or links displayed normally
I also attempted to package ROCM on musl.
But why is there no such pushback agains linux kernel?
OpenCode Support
Upcoming changes to the tado° API
Allow Mac users to use Apple native containerization
Support for the Containerization Framework on macOS
Facilitate ConfigMap rollouts / management
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
Comments (0)
No comments yet. Start the discussion.