'kubernetes rolling update after all client connections down
How to use rolling update in daemonset? Is it possible to check all client connects are done then go to do update and delete pod? Since our client connection time is too long to estimate shutdown pod timing. (We already use helm chart for rolling update now.)
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|