d229d52292
This changes unsequenced chart group deployments, such that each chart in the group is deployed in parallel, including the install/upgrade, wait, and tests. Previously, whether and when to wait was entangled with whether or not the chart group was sequenced, since running helm install/upgrade's native wait (which cannot be run later) and armada's labels based wait, delayed (or even prevented in the case of failure) the next chart from being deployed, which is the intention for sequenced, but not for unsequenced. With this patchset, sequencing and waiting are now orthogonal. Hence we can now allow the user to explictly specify whether to wait, which this patchset does for the case of helm's native wait via a new `wait.native.enabled` flag, which defaults to true. Previously, armada's labels-based wait sometimes occurred both between charts and at the end of the chart group. It now occurs once directly after chart deployment. Previously, passing armada's --wait was documented to be equivalent to forcing sequencing of chart groups, however helm tests did not run in sequence as they normally would with sequenced chart groups, they now do. Since chart deploys can now occur in parallel, log messages for each become interleaved, and thus when armada is deploying a chart, log messages are updated to contain identifying information about which chart deployment they are for. Change-Id: I9d13245c40887712333aaccfb044dcdc4b83988e |
||
---|---|---|
.. | ||
__init__.py | ||
armada.py | ||
chart_deploy.py | ||
chartbuilder.py | ||
document.py | ||
k8s.py | ||
manifest.py | ||
override.py | ||
release_diff.py | ||
test.py | ||
tiller.py | ||
wait.py |