github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify limit/requests flags in kubectl run

Browse Source
This commit is contained in:
Janet Kuo
2016-04-22 17:08:34 -07:00
parent 0db3ca4b50
commit 57c2a28b92
4 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/yaml/kubectl/kubectl_run.yaml
View File

@@ -45,7 +45,7 @@ options:
If the pod is started in interactive mode or with stdin, leave stdin open after the first attach completes. By default, stdin will be closed after the first attach completes.
- name: limits
usage: |
The resource requirement limits for this container. For example, 'cpu=200m,memory=512Mi'
The resource requirement limits for this container. For example, 'cpu=200m,memory=512Mi'. Note that server side components may assign limits depending on the server configuration, such as limit ranges.
- name: no-headers
default_value: "false"
usage: When using the default output, don't print headers.
@@ -73,7 +73,7 @@ options:
Number of replicas to create for this container. Default is 1.
- name: requests
usage: |
The resource requirement requests for this container. For example, 'cpu=100m,memory=256Mi'
The resource requirement requests for this container. For example, 'cpu=100m,memory=256Mi'. Note that server side components may assign requests depending on the server configuration, such as limit ranges.
- name: restart
default_value: Always
usage: |