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

..

client

Replicate base resource for lists functionality (#89)

2021-05-05 10:09:22 -04:00

__init__.py

Issue #1, Issue #2: Move more content into collection, fix tests.

2020-01-30 13:51:43 -06:00

ansiblemodule.py

Enable the ansible turbo module (#68)

2021-04-23 13:10:46 -04:00

apply.py

Replicate apply method in the DynamicClient (#45)

2021-04-22 14:58:53 -04:00

args_common.py

add option proxy_headers for k8s modules (#58)

2021-04-28 08:44:57 +02:00

common.py

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

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

exceptions.py

Replicate apply method in the DynamicClient (#45)

2021-04-22 14:58:53 -04:00

hashes.py

Add configmap/secret hash functionality (#48)

2021-04-20 08:27:25 -04:00

helm.py

helm: handle multiline output (#64)

2021-04-20 12:07:28 +05:30

k8sdynamicclient.py

Replicate apply method in the DynamicClient (#45)

2021-04-22 14:58:53 -04:00