Enhancement of Container Update Function

Registered by Masaki UENO

In the current implementation, when users invoke update operation of ConfigMaps and Secrets, all Pods are restarted even if they not uses those updated CMs and Secrets. This modification aims to remove this limitation.
Methods to achieve this feature needs more investigation. The below points are important for removing the current limitation:

- The method to filter and determine Pods that needs restart by the change of CMs and Secrets
- Need k8s python client support for achieve filtering by CMs and secrets.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Masaki UENO
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.