You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-apps/4017-pod-index-label/README.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -767,9 +767,7 @@ Describe them, providing:
767
767
- Estimated amount of new objects: (e.g., new Object X for every existing Pod)
768
768
-->
769
769
New pod label of size 34B plus value of size N where N is the number of digits in the pod ordinal.
770
-
Worst case for N would be the max number of pods per node * max number of nodes. Per the docs on [large clusters](https://kubernetes.io/docs/setup/best-practices/cluster-large/) this would be 110 pods/node * 5000 nodes = 550,000 (6 digits).
771
-
772
-
So max label size would be 34 + 6 = 40B.
770
+
Worst case for N would be the max number of pods per cluster. Per the docs on [large clusters](https://kubernetes.io/docs/setup/best-practices/cluster-large/) this is 150,000 (6 digits). So max label size would be 34 + 6 = 40B.
773
771
774
772
###### Will enabling / using this feature result in increasing time taken by any operations covered by existing SLIs/SLOs?
0 commit comments