Skip to content

Commit 202ea47

Browse files
committed
Fixed footnote formatting
1 parent 527f0ae commit 202ea47

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/openshift-cluster-maximums-major-releases.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Tested Cloud Platforms for {product-title} 4.x: Amazon Web Services, Microsoft A
2222

2323
| Number of Pods per node
2424
| 250
25-
| 500 footnote:[podspernodemajorrelease,This was tested on a cluster with 100 worker nodes with 500 Pods per worker node. The default `maxPods` is still 250. To get to 500 `maxPods`, the cluster must be created with a `maxPods` set to `500` using a custom KubeletConfig. If you need 500 user pods, you need a `hostPrefix` of `22` because there are 10-15 system Pods already running on the node. The maximum number of Pods with attached Persistent Volume Claims (PVC) depends on storage backend from where PVC are allocated. In our tests, only OpenShift Container Storage v4 (OCS v4) was able to satisfy the number of Pods per node discussed in this document.]
25+
| 500 footnoteref:[podspernodemajorrelease,This was tested on a cluster with 100 worker nodes with 500 Pods per worker node. The default `maxPods` is still 250. To get to 500 `maxPods`, the cluster must be created with a `maxPods` set to `500` using a custom KubeletConfig. If you need 500 user pods, you need a `hostPrefix` of `22` because there are 10-15 system Pods already running on the node. The maximum number of Pods with attached Persistent Volume Claims (PVC) depends on storage backend from where PVC are allocated. In our tests, only OpenShift Container Storage v4 (OCS v4) was able to satisfy the number of Pods per node discussed in this document.]
2626

2727
| Number of Pods per core
2828
| There is no default value.

0 commit comments

Comments
 (0)