Bug 1473664 - [DOCS] pods-per-core 0 value is not documented
Summary: [DOCS] pods-per-core 0 value is not documented
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Ashley Hardin
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-21 12:01 UTC by Sergi Jimenez Romero
Modified: 2020-12-14 09:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-04 17:42:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sergi Jimenez Romero 2017-07-21 12:01:50 UTC
Document URL: 

(Best option I could find) https://docs.openshift.com/container-platform/3.5/scaling_performance/host_practices.html

Section Number and Name: 

2.10.1. Setting Maximum Pods Per Node

Describe the issue:

Setting pods-per-core to 0 disables the setting completely and that is not documented or it's rather hard to find.

Suggestions for improvement:

Adding a note describing how to disable pods-per-core setting it to 0.

Additional information: 

This was found on Kubernetes documentation but not in OCP.

Comment 4 openshift-github-bot 2017-07-21 21:43:24 UTC
Commits pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/16dff7b99a3dfe8c2f69bf950607884abcb42dcd
Bug 1473664 document pods-per-core value 0

As per https://bugzilla.redhat.com/1473664, setting `pods-per-core` to 0
disables this limit.

Documented at https://kubernetes.io/docs/admin/kubelet/

https://github.com/openshift/openshift-docs/commit/03f0dbd27c4c3286cd79e39bb06fb1d1d43db334
Merge pull request #4830 from tripledes/pods_per_core_zero_value

Bug 1473664 document pods-per-core value 0


Note You need to log in before you can comment on or make changes to this bug.