Merge pull request #249289 from cadenmarchese/tag-limit

Specify limit of 10 user defined tags for an ARO cluster

Author: prmerger-automator[bot]

articles/openshift/support-policies-v4.md

@@ -37,6 +37,7 @@ Certain configurations for Azure Red Hat OpenShift 4 clusters can affect your cl
 * 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.
 * 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.
 * If you are making use of infrastructure nodes, do not run any undesignated workloads on them as this may affect the Service Level Agreement and cluster stability. Also, it is strongly recommended to have at least 3 infrastructure nodes; one in each availability zone. See [Deploy infrastructure nodes in an Azure Red Hat OpenShift (ARO) cluster](howto-infrastructure-nodes.md) for more information.
+* OpenShift relies on the ability to automatically tag Azure resources. If you have configured a tagging policy, do not apply more than 10 user-defined tags to resources in the managed resource group.
 
 ## Supported virtual machine sizes