Skip to content

✨ Add support for 'fast' channelGroupType in ROSA provider #5587

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 15, 2025
Merged

✨ Add support for 'fast' channelGroupType in ROSA provider #5587

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions config/crd/bases/controlplane.cluster.x-k8s.io_rosacontrolplanes.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,6 +87,7 @@ spec:
description: OpenShift version channel group, default is stable.
enum:
- stable
- fast
- candidate
- nightly
type: string
Expand Down
5 changes: 4 additions & 1 deletion controlplane/rosa/api/v1beta2/rosacontrolplane_types.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,9 @@ const (
// Stable channel group is the default channel group for stable releases.
Stable ChannelGroupType = "stable"

// Fast channel group is for fast channel releases.
Fast ChannelGroupType = "fast"

// Candidate channel group is for testing candidate builds.
Candidate ChannelGroupType = "candidate"

Expand Down Expand Up @@ -107,7 +110,7 @@ type RosaControlPlaneSpec struct { //nolint: maligned

// OpenShift version channel group, default is stable.
//
// +kubebuilder:validation:Enum=stable;candidate;nightly
// +kubebuilder:validation:Enum=stable;fast;candidate;nightly
// +kubebuilder:default=stable
ChannelGroup ChannelGroupType `json:"channelGroup"`

Expand Down
4 changes: 2 additions & 2 deletions docs/book/src/topics/rosa/upgrades.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,14 @@

Upgrading the OpenShift version of the control plane is supported by the provider. To perform an upgrade you need to update the `version` in the spec of the `ROSAControlPlane`. Once the version has changed the provider will handle the upgrade for you.

Upgrading y-stream version ex; v4.16.x to v4.17.x required the version gate acknowledgement. By default the versionGate is set to WaitForAcknowledge in the `ROSAControlPlane` CR. When upgrading to y-stream version the versionGate should be set to Acknowledge or AlwaysAcknowledge.
Upgrading y-stream version ex; v4.16.x to v4.17.x required the version gate acknowledgement. By default the versionGate is set to WaitForAcknowledge in the `ROSAControlPlane` CR. When upgrading to y-stream version the versionGate should be set to Acknowledge or AlwaysAcknowledge.

##### Note:
When the versionGate is set to 'Acknowledge', it will revert to 'WaitForAcknowledge' once the upgrade is successfully completed. However, if the versionGate is set to 'AlwaysAcknowledge', it will remain set to 'AlwaysAcknowledge' after the upgrade is successfully completed.

The available upgrades versions for the `ROSAControlPlane` will be listed under `ROSAControlPlane.status.availableUpgrades`

The version channel group `ROSAControlPlane.spec.channelGroup` default to stable. However, it can be set to candidate or nightly. Changing the version channel group will change the `ROSAControlPlane.status.availableUpgrades` accordingly.
The version channel group `ROSAControlPlane.spec.channelGroup` default to stable. However, it can be set to fast, candidate, or nightly. Changing the version channel group will change the `ROSAControlPlane.status.availableUpgrades` accordingly. Note that the use of channel groups other than stable may require additional permissions.

The Upgrade state can be checked in the conditions under `ROSAControlPlane.status`.

Expand Down