Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Allow installs to proceed if no v2 and v3 release exists during migration #471

Merged
merged 1 commit into from Jun 26, 2020

Conversation

saada
Copy link
Contributor

@saada saada commented Jun 25, 2020

  • When rolling out migrations across many clusters, there could be some new helm releases that were migrated. For example, if we have DEV, UAT, and PROD environments; DEV might have already migrated v2 to v3 releases, UAT might still need to do the migration, while PROD might not have had the v2 releases at all. This bugfix allows all 3 scenarios to work as expected.

@hiddeco hiddeco changed the title bugfix: allow installs to proceed if no v2 and v3 release exists during migration Allow installs to proceed if no v2 and v3 release exists during migration Jun 25, 2020
@hiddeco hiddeco added the bug Something isn't working label Jun 25, 2020
@hiddeco hiddeco force-pushed the enhancement/helm-2to3-migrate branch from 19ffc17 to fe158e7 Compare June 25, 2020 16:53
Copy link
Contributor

@rndstr rndstr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm 👌

@saada saada force-pushed the enhancement/helm-2to3-migrate branch from 609d861 to 5a58d84 Compare June 25, 2020 18:56
…ng migration

bugfix: allow installs to proceed if no v2 and v3 release exists during migration
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants