Better 'helm list' visibility into state of pending upgrades

[bodepd]

The below logs demonstrate how Helm updates the revision at the end of an upgrade.

2017/03/03 19:23:13 client.go:416: Add/Modify event for jenkins-staging-public-jenkins-9vovw: ADDED
2017/03/03 19:23:13 client.go:452: jenkins-staging-public-jenkins-9vovw: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
2017/03/03 19:23:21 storage.go:133: Getting release history for 'jenkins-staging-private'
2017/03/03 19:23:35 client.go:416: Add/Modify event for jenkins-staging-public-jenkins-9vovw: MODIFIED
2017/03/03 19:23:35 release_server.go:862: Hooks complete for post-upgrade jenkins-staging-public
2017/03/03 19:23:35 storage.go:53: Updating "jenkins-staging-public" (v1) in storage
2017/03/03 19:23:35 storage.go:45: Create release "jenkins-staging-public" (v2) in storage

during the upgrade, the state listed for a release via helm list is whatever the state happened to be before this upgrade takes place, both the revision number and state only ever get updated once a deployment has either passed or failed.

I have 3 suggestions related to this:

1. Add more states to the STATUS column of helm list. The simplest one, would be a pending or in-progress status so that I can know the state of a release is that it is working. Without this status, I have to either go into kubernetes or view the logs of tiller to understand what the current state of my infra is.
2. Show what revision is currently in progress, this could either be done by updating the revision as soon as something starts, or by adding a new column, which is desired revision
3. Include time of last action, not just the time of when the last thing updated.

[thomastaylor312]

I would really love to have this feature and I'll probably take a crack at it once I finish other work that is in flight

[technosophos]

Bumping to 2.5.0, since I haven't seen a PR for this feature yet.

[technosophos]

This has had no activity for 60 days, so I am pulling it off the release milestones and marking it as Help Wanted.

[ata18]

@thomastaylor312 I would like to work on this feature, if you haven't started looking into it already.

[thomastaylor312]

@at1012 Yes, feel free to do that. Thank you!

[ata18]

@thomastaylor312 @bodepd Will the following work for you? It shows both the old and new release with a pending status while performing the upgrade and once the upgrade completes/fails the older release will be removed and the new release's status gets updated accordingly. You need to use helm ls --all in order to see the pending ones. By default helm ls only shows the deployed ones.

helm upgrade -f config.yaml excited-lamb stable/mariadb --wait
Release "excited-lamb" has been upgraded. Happy Helming!

--- k8s.io/helm ‹at-helm-list*➔ M?› » helm ls --all
NAME            REVISION        UPDATED                         STATUS          CHART           NAMESPACE
excited-lamb    2               Tue Jul 11 16:55:44 2017        DEPLOYED        mariadb-0.6.3   default
excited-lamb    3               Tue Jul 11 17:04:24 2017        PENDING         mariadb-0.6.3   default

--- k8s.io/helm ‹at-helm-list*➔ M?› » helm ls --all
NAME            REVISION        UPDATED                         STATUS          CHART           NAMESPACE
excited-lamb    3               Tue Jul 11 17:04:24 2017        DEPLOYED        mariadb-0.6.3   default

Currently with my changes in place, the updated-time shows the time when the upgrade was initiated. When you said 3. Include time of last action, not just the time of when the last thing updated., is that what you meant?