Skip to content

Commit c001e46

Browse files
authored
Merge pull request #193458 from cadenmarchese/vm-poweroff-support
Clarify ARO support policy for VM power state, deny assignment
2 parents 2c45447 + 65634ce commit c001e46

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/openshift/support-policies-v4.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,9 @@ Certain configurations for Azure Red Hat OpenShift 4 clusters can affect your cl
1919
## Cluster configuration requirements
2020

2121
* All OpenShift Cluster operators must remain in a managed state. The list of cluster operators can be returned by running `oc get clusteroperators`.
22-
* The cluster must have a minimum of three worker nodes and three control plane nodes. Don't have taints that prevent OpenShift components to be scheduled. Don't scale the cluster workers to zero, or attempt a graceful cluster shutdown.
22+
* The cluster must have a minimum of three worker nodes and three manager nodes.
23+
* Don't scale the cluster workers to zero, or attempt a cluster shutdown. Deallocating or powering down any virtual machine in the cluster resource group is not supported.
24+
* Don't have taints that prevent OpenShift components to be scheduled.
2325
* Don't remove or modify the cluster Prometheus and Alertmanager services.
2426
* Don't remove Service Alertmanager rules.
2527
* Security groups can't be modified. Any attempt to modify security groups will be reverted.
@@ -32,6 +34,7 @@ Certain configurations for Azure Red Hat OpenShift 4 clusters can affect your cl
3234
* Non-RHCOS compute nodes aren't supported. For example, you can't use a RHEL compute node.
3335
* Don't place policies within your subscription or management group that prevent SREs from performing normal maintenance against the Azure Red Hat OpenShift cluster. For example, don't require tags on the Azure Red Hat OpenShift RP-managed cluster resource group.
3436
* Do not run extra workloads on the control plane nodes. While they can be scheduled on the control plane nodes, it will cause extra resource usage and stability issues that can affect the entire cluster.
37+
* Don't circumvent the deny assignment that is configured as part of the service, or perform administrative tasks that are normally prohibited by the deny assignment.
3538

3639
## Supported virtual machine sizes
3740

0 commit comments

Comments
 (0)