-
Notifications
You must be signed in to change notification settings - Fork 105
feat: add z-stream upgrade configuration support via static Helm values #3850
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
Draft
machi1990
wants to merge
1
commit into
main
Choose a base branch
from
machi1990/add-z-stream-managed-upgrade-config-next
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8 changes: 8 additions & 0 deletions
8
cluster-service/helm-charts/cluster-service/static-configs/ocp-versions-current.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| defaultVersion: | ||
| channelGroupName: stable | ||
| version: "4.20.8" | ||
| channelGroups: | ||
| - url: "https://api.openshift.com/api/upgrades_info/graph" | ||
| channelGroupName: stable | ||
| minVersion: "4.19.0" | ||
| maxVersion: "4.20.9" |
34 changes: 34 additions & 0 deletions
34
cluster-service/helm-charts/cluster-service/static-configs/ocp-versions-next.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| defaultVersion: | ||
| channelGroupName: stable | ||
| version: "4.20.8" | ||
| channelGroups: | ||
| - url: "https://api.openshift.com/api/upgrades_info/graph" | ||
| channelGroupName: stable | ||
| minVersion: "4.19.0" | ||
| maxVersion: "4.20.9" | ||
| minorVersionsConfiguration: | ||
| - name: "4.19" | ||
| zStreamUpgradeConfig: | ||
| enabled: true | ||
| targetVersion: "4.19.21" | ||
| - name: "4.20" | ||
| zStreamUpgradeConfig: | ||
| enabled: true | ||
| targetVersion: "4.20.8" | ||
| - url: "https://api.openshift.com/api/upgrades_info/graph" | ||
| channelGroupName: candidate | ||
| minVersion: "4.19.7" | ||
| maxVersion: "" | ||
| minorVersionsConfiguration: | ||
| - name: "4.19" | ||
| zStreamUpgradeConfig: | ||
| enabled: true | ||
| targetVersion: "4.19.22" | ||
| - name: "4.20" | ||
| zStreamUpgradeConfig: | ||
| enabled: true | ||
| targetVersion: "4.20.10" | ||
| - url: "https://multi.ocp.releases.ci.openshift.org/graph" | ||
| channelGroupName: nightly | ||
| minVersion: "4.19.0-0.nightly-20200101" | ||
| maxVersion: "" | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really seems like the backend should be in charge of this and CS should just accept an explicit, opaque value to install and deal with it. Why are we adding more logic to CS for this when we're just going to have to migrate it later?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. However...
By the time the decision to move CS to the RP, some features were already at work (in progress) and this was one of them. At that time, it was agreed (with leadership) that we'll continue to work on those features as is in CS and when the migration is fully ongoing, we'll migrate everything including new code. The motivation for this message was so that the migration doesn't slow feature development.
cc @davidffrench @deads2k to chime in for additional insights
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to @machi1990 comment, the implementation was already in progress. I would like us to ensure successful delivery of managed z stream upgrades as early as possible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see a good half-dozen open PRs by Miguel in this repo right now - by what metric is the migration not fully ongoing?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should continue to ask everytime if it something should be added to CS or the backend directly, as time passes, the answer will increasingly become more weighted to the RP.
You are correct. A different phrasing of Manyandas comment is that we decided to implement this functionality in CS when it started in December as it would allow us to support this in production the fastest, and this logic in CS will be a part of the migration effort over the coming months.