Bug 1293454 - [DOCS] Add node config setting for kubeletArguments for setting max pods
[DOCS] Add node config setting for kubeletArguments for setting max pods
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
3.1.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Vikram Goyal
Vikram Goyal
Vikram Goyal
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-21 14:09 EST by Ryan Howe
Modified: 2015-12-21 14:09 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ryan Howe 2015-12-21 14:09:26 EST
Document URL: https://docs.openshift.com/enterprise/3.1/install_config/master_node_configuration.html#node-configuration-files

Section Number and Name: https://docs.openshift.com/enterprise/3.1/install_config/master_node_configuration.html#node-configuration-files

Describe the issue:  Add info on setting kubelte Args for max pods


Additional information: 

ax pods per node is set on the node - you can add in the stanza to the node config YAML file to set it:

kubeletArguments:
  max-pods:
  - "100"

The string is important - this stanza passes arguments directly to the Kubelet invocation (so any arg you can pass to a Kubelet you can pass via this config)

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