THREESCALE-8502 3scale operator to have an ability to deal with multiple release paths #781
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.
what
THREESCALE-8502 3scale operator to have an ability to deal with multiple release paths
how
Upgrade procedure in reconciliation loop. Actually, most of it was already in the normal reconciliation loop. Only DC triggers and pod template labels were moved
custom release upgrade procedure has been removed.
verification steps
Deploy 2.12
wait for deployment to be ready
Check apimanager version
Check imagestreams, for instance amp-apicast
Check deployment config's triggers, for instance, apicast-production
Kill 2.12 operator with
CTRL+c
and move git workspace toapimanager-upgrade-in-main-reconciler-loop
branchRun the controller to perform upgrade
wait for deployment to be ready
Check apimanager version has been updated to 2.13
Check that imagestream objects have a new tag for the 2.13
Check that deployment config triggers has reference updated to 2.13