Merge pull request #22953 from ahardin-rh/hostprefix

Bug 1846845, removed hostprefix value

Author: ahardin-rh

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

@@ -22,7 +22,7 @@ Tested Cloud Platforms for {product-title} 4.x: Amazon Web Services, Microsoft A
 
 | Number of Pods per node
 | 250
-| 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 `hostPrefix` of `22` in the `install-config.yaml` file and `maxPods` set to `500` using a custom KubeletConfig. The maximum number of Pods with attached Persistant 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.]
+| 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.]
 
 | Number of Pods per core
 | There is no default value.