Skip to content

Commit 6aea1a6

Browse files
committed
- if pods require PVC to be attached to them then pods per node maximum value will
be limited by storage backend from Persistant Volume Claims are created.
1 parent cd59471 commit 6aea1a6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/openshift-cluster-maximums.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@
2525
| 250
2626
| 250
2727
| 250
28-
| 500 footnoteref:[podspernode, 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.]
28+
| 500 footnoteref:[podspernode, 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.]
2929

3030
| Number of pods per core
3131
| There is no default value.

0 commit comments

Comments
 (0)