Skip to content

Commit deac802

Browse files
committed
Added link for infrastructure node guidance.
1 parent f6adeac commit deac802

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/openshift/howto-infrastructure-nodes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: template-how-to
1414

1515
ARO allows you to use infrastructure machine sets to create machines that only host infrastructure components, such as the default router, the integrated container registry, and the components for cluster metrics and monitoring. These infrastructure machines don't incur OpenShift costs; they only incur Azure Compute costs.
1616

17-
In a production deployment, it's recommended that you deploy three machine sets to hold infrastructure components. Each of these nodes can be deployed to different availability zones to increase availability. This type of configuration requires three different machines sets; one for each availability zone.
17+
In a production deployment, it's recommended that you deploy three machine sets to hold infrastructure components. Each of these nodes can be deployed to different availability zones to increase availability. This type of configuration requires three different machines sets; one for each availability zone. For infrastructure node sizing guidance, see [Recommended infrastructure practices](https://docs.openshift.com/container-platform/4.14/scalability_and_performance/recommended-performance-scale-practices/recommended-infrastructure-practices.html).
1818

1919
## Qualified workloads
2020

0 commit comments

Comments
 (0)