blocked-edges/4.10.0-fc.4-alibaba-storage-fixes: Example conditional update #1464
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.
Following up on 38028a8 (#1437) with a new invented, demo conditional update. The earlier demo worked locally, but did not excercise Insights tooling, because Insights only bumped their openshift/api vendor in fc.3:
So fc.0 and fc.1 with the previous conditional update were having that unrecognized-to-the-older-insights-operator property dropped. This commit adds a new demo conditional edge for 4.10 -> fc.4, so we can look at running fc.3 clusters to see
conditionalUpdatesin Insights.