Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating aro-faq with new details #43386

Closed
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions articles/openshift/openshift-faq.md
Expand Up @@ -134,7 +134,7 @@ Refer to [Choosing the right number of fault domains for virtual machine scale s

## Is there a way to manage pod placement?

With the impending customer-admin update, customers will have the ability to get nodes and view labels.  This will provide a way to target any VM in the scale set.
Customers have the ability to get nodes and view labels as the customer-admin.  This will provide a way to target any VM in the scale set.

Caution must be used when using specific labels:

Expand All @@ -144,7 +144,7 @@ Caution must be used when using specific labels:

## What is the maximum number of pods in an ARO cluster?  What is the maximum number of pods per node in ARO?

Refer to [upstream OpenShift docs](https://docs.openshift.com/container-platform/3.11/scaling_performance/cluster_limits.html#scaling-performance-current-cluster-limits) for more details. Red Hat OpenShift 3.11 has a 250-pod/node limit, whereas [ARO has a 20-compute node limit](https://docs.microsoft.com/azure/openshift/openshift-faq#what-cluster-operations-are-available), so that caps the maximum number of pods supported in an ARO cluster to 250*20 = 5000.
Refer to [upstream OpenShift docs](https://docs.openshift.com/container-platform/3.11/scaling_performance/cluster_limits.html#scaling-performance-current-cluster-limits) for more details. Red Hat OpenShift 3.11 has a 50-pod/node limit, whereas [ARO has a 20-compute node limit](https://docs.microsoft.com/azure/openshift/openshift-faq#what-cluster-operations-are-available), so that caps the maximum number of pods supported in an ARO cluster to 250*20 = 5000.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this math need to be changed to 50*20 = 1000 being that the number changed from 250 -> 50?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This link doesn't exist anymore and linking to this documentation that once existed showed the limits of the OpenShift Container Platform and not Azure Red Hat OpenShift with having a limit of 250 pods per node. Rewording this to show that Azure Red Hat OpenShift only allows a capacity of 50 pods per node as a capacity and not link to the documentation will rectify the discrepancy. @sakthi-vetrivel


## Can we specify IP ranges for deployment on the private VNET, avoiding clashes with other corporate VNETs once peered?

Expand Down