After installing a chart successfully, I ran a helm upgrade with modified values. This caused a pre-upgrade hook to fail, since the hook tried to create a job that already existed (since it wasn't deleted before the upgrade).
At that point, helm ls would show the first revision as DEPLOYED. The second revision would appear only with helm ls -a. After deleting the job and rerunning helm upgrade, I noticed that there were now two releases of the same chart, both marked as DEPLOYED -- the first one, before the PENDING_UPGRADE revision, and the most recent.
$ helm ls
NAME REVISION UPDATED STATUS CHART NAMESPACE
comfy 1 Thu Sep 14 18:24:07 2017 DEPLOYED comfy-1.0.0 default
comfy 4 Thu Sep 14 18:47:03 2017 DEPLOYED comfy-1.0.0 default
As expected helm status shows the status of the most recent deployed revision. Helm history for the release shows the following:
REVISION UPDATED STATUS CHART DESCRIPTION
1 Thu Sep 14 18:24:07 2017 DEPLOYED comfy-1.0.0 Install complete
2 Thu Sep 14 18:46:33 2017 PENDING_UPGRADE comfy-1.0.0 Preparing upgrade
3 Thu Sep 14 18:46:52 2017 SUPERSEDED comfy-1.0.0 Preparing upgrade
4 Thu Sep 14 18:47:03 2017 DEPLOYED comfy-1.0.0 Upgrade complete
This conflicts with my understanding of what DEPLOYED means -- I thought that for any release, there could only be one revision that is DEPLOYED, corresponding to the kubernetes objects currently in the cluster. Should I be interpreting the meaning of DEPLOYED differently or is this behavior not expected?
After installing a chart successfully, I ran a
helm upgradewith modified values. This caused apre-upgradehook to fail, since the hook tried to create a job that already existed (since it wasn't deleted before the upgrade).At that point,
helm lswould show the first revision asDEPLOYED. The second revision would appear only withhelm ls -a. After deleting the job and rerunninghelm upgrade, I noticed that there were now two releases of the same chart, both marked asDEPLOYED-- the first one, before thePENDING_UPGRADErevision, and the most recent.As expected
helm statusshows the status of the most recent deployed revision. Helm history for the release shows the following:This conflicts with my understanding of what
DEPLOYEDmeans -- I thought that for any release, there could only be one revision that isDEPLOYED, corresponding to the kubernetes objects currently in the cluster. Should I be interpreting the meaning ofDEPLOYEDdifferently or is this behavior not expected?