Technology Preview: Hibernating and Resuming ROSA Clusters

Updated -

Red Hat OpenShift Service on AWS (ROSA) clusters is currently developing a hibernation feature, allowing clusters to be shut down and resumed. However, it's essential to understand the terms and conditions associated with using this feature, especially under exceptions or technology previews. This article is intended for those internal users and some external users through support exception have early access to this feature. If you are an external customer interested in participating in the hibernation technology preview, please open a support case requesting early access to this feature.

Note: Shutting down partial or all nodes of ROSA cluster is not supported under SLA. Refer to the article for the feature behavior under SLA. Hibernation is also not available yet.

Terms and Conditions

  1. Technology Preview Agreement: By using the hibernation/resume feature, you acknowledge that it falls under the Technology Preview category. This implies that there might be a need to recreate the cluster as per the terms of the Technology Preview.

  2. Non-Production Usage: Ensure that the hibernation/resume feature is tested only on non-production clusters. These clusters should not host critical workloads or data that cannot be recovered.

  3. Limited Support: From the moment a cluster is hibernated until it's fully resumed, it will be under Limited Support as per the ROSA SLA.

  4. OpenShift Version: The cluster should have been initially set up on an OpenShift version 4.5 or later.

  5. Hibernation Duration: A cluster should not be in hibernation for more than 30 consecutive days. It's the user's responsibility to monitor this duration and ensure timely resumption.

  6. Avoiding End-of-Life (EOL): Ensure that the OpenShift version on the hibernated cluster doesn't reach its EOL within 30 days from the start of hibernation. This is to allow ample time for necessary upgrades.

  7. MachineConfigPools Status: Before hibernating, verify that the MachineConfigPools are not updating. Use the command:

    oc get machineconfigpool

  8. Cluster Operators Status: Ensure all cluster operators are in the correct state before hibernation:

    oc get clusteroperators

  9. Hibernation Intervals: After resuming a hibernated cluster, wait for at least 2 hours before initiating another hibernation.

  10. Resumption Time: Be prepared for a wait time of up to 45 minutes for the cluster to become ready after resumption.

  11. AWS Local Zones: Hibernated clusters should not utilize machine pools in AWS Local Zones.

By adhering to these guidelines and terms, you can effectively use the hibernation feature on ROSA/OSD clusters while ensuring the safety and integrity of your data and workloads.

Comments