Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide pre-upgrade job unless feature flag set. #1542

Merged
merged 1 commit into from
Feb 25, 2020

Conversation

absoludity
Copy link
Contributor

@absoludity absoludity commented Feb 25, 2020

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.

@absoludity absoludity merged commit 98f34a9 into vmware-tanzu:master Feb 25, 2020
@absoludity absoludity deleted the dont-pre-upgrade-yet branch February 25, 2020 23:09
@andresmgot
Copy link
Contributor

Thanks for quickly fixing the issue!

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.

I agree, we could open an issue for this. We could at least check that for minor and patch versions the upgrade works as expected.

@davidkarlsen
Copy link
Contributor

Great - just rolled it out - works as designed.
Thanks!

@absoludity
Copy link
Contributor Author

Thanks for quickly fixing the issue!

Np, just note that we need to remove the condition as when we're releasing the next kubeapps version, because this is required for the postgresql support.

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.

I agree, we could open an issue for this. We could at least check that for minor and patch versions the upgrade works as expected.

#1544

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants