Hide pre-upgrade job unless feature flag set. #1542
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had landed the pre-upgrade template after the most recent kubeapps release (1.8.2) thinking that it was safe, as the next chart release would include support for the cache invalidation, but this was not a safe assumption, since we had a chart release on Monday to update the nginx image in #1536 . Since this release included the pre-upgrade template which calls a new command to invalidate cache, the upgrade fails as we have not yet released a kubeapps version including the cache invalidation (see https://kubernetes.slack.com/archives/C9D3TSUG4/p1582667703003300)
I'll land to get the release out.
I'm also keen to update our CI so that on a chart bump, we actually test the upgrade from the previous chart version and don't release.