OpenShif-CY24Q1- Updating ROSA!

See how easy managing your container platform can be!

Updating Red Hat OpenShift Service on AWS (ROSA)

The Kubernetes project maintains release branches for the most recent three minor releases (1.28, 1.27, 1.26). Kubernetes 1.19 and newer receive approximately 1 year of patch support. Kubernetes 1.18 and older received approximately 9 months of patch support.
Kubernetes versions are expressed as x.y.z, where x is the major version, y is the minor version, and z is the patch version, following Semantic Versioning terminology.
More information in the version skew policy document.

Releases | Kubernetes

Clusters | Red Hat OpenShift Cluster Manager

august-rosa | Red Hat OpenShift Cluster Manager

Note: In the event of Critical security concerns
(new window or tab)
 (CVEs) that significantly impact the security or stability of the cluster, updates may be automatically scheduled by Red Hat SRE to the latest z-stream version not impacted by the CVE within 48 hours after customer notifications.

Individual updates
Schedule each update individually. Take into consideration end of life dates from the lifecycle policy
(new window or tab)
 when planning updates.
Recurring updates
The cluster will be automatically updated based on your preferred day and start time when new patch updates (z-stream
(new window or tab)
) are available. When a new minor version is available, you'll be notified and must manually allow the cluster to update to the next minor version.
Info alert:
Recurring updates occur when a new patch (z-stream) update becomes available at least 2 days prior to your selected start time.
Select a day and start time
Sunday
00:00 UTC
Node draining

You may set a grace period for how long pod disruption budget-protected workloads will be respected during updates. After this grace period, any workloads protected by pod disruption budgets that have not been successfully drained from a node will be forcibly evicted.

Grace period
1 hour