Mike Graves 0bbc9ca999 Account for updated pods when waiting on DaemonSet (#102) ...

* Account for updated pods when waiting on DaemonSet

The exising logic that's used to determine when a DaemonSet is ready
fails to account for the fact that a RollingUpdate first kills the pod
and then creates a new one. Simply checking if the
desiredNumberScheduled equals the numberReady will succeed in cases
when the old pod takes time to shut down, and would report that the new
Deployment is ready despite the fact that the old pod has not been
replaced, yet.

* Add changelog fragment

2021-05-19 09:29:22 -04:00

..

action

k8s loop flattening for template argument (#49)

2021-04-22 19:28:07 +02:00

connection

kubectl: correct usage in console (#204)

2020-08-31 09:29:27 +05:30

doc_fragments

Replace openshift client with kubernetes client (#96)

2021-05-06 14:44:17 -04:00

filter

Remove empty docstring in filter plugin (#106)

2021-05-18 15:34:41 -04:00

inventory

Replace openshift client with kubernetes client (#96)

2021-05-06 14:44:17 -04:00

lookup

Replace openshift client with kubernetes client (#96)

2021-05-06 14:44:17 -04:00

module_utils

Account for updated pods when waiting on DaemonSet (#102)

2021-05-19 09:29:22 -04:00

modules

k8s - patch existing resource (#90)

2021-05-19 11:03:11 +02:00