Bug 1293454 - [DOCS] Add node config setting for kubeletArguments for setting max pods
Summary: [DOCS] Add node config setting for kubeletArguments for setting max pods
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: brice
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-21 19:09 UTC by Ryan Howe
Modified: 2017-11-30 03:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-30 03:41:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan Howe 2015-12-21 19:09:26 UTC
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)

Comment 1 brice 2017-11-30 03:41:24 UTC
Looks like this was added into the 3.1 docs, and has been in the same location since:

https://docs.openshift.com/enterprise/3.1/admin_guide/manage_nodes.html#configuring-node-resources

I'll move this BZ to closed. Ryan, if there's anything else for this BZ, please let me know.


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