This repository has been archived by the owner on May 6, 2022. It is now read-only.
Fix ServiceInstance restore process in migration job #2735
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.
This PR is a
What this PR does / why we need it:
This short PR fixes the migration process between a version with APIserver and the crds.
During the restore process for ServiceInstance, before creating the resource from the backup data, all information about ClusterServiceClass reference is removed. This information is restored in the update process after creation.
If the creation process fails, then we lose information about ClusterServiceClass reference (before the process the data is overwritten with an empty value). This PR fixes this issue.
Please leave this checklist in the PR comment so that maintainers can ensure a good PR.
Merge Checklist:
breaking the chart release and existing clients who provide a
flag that will get an error when they try to update