kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update index.md

pull/2503/head
scjane 2017-02-13 10:40:57 +08:00 committed by Andrew Chen
parent 9f3ab47c8b
commit 87401ac54b
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/user-guide/jobs/expansions/index.md
View File

@ -111,7 +111,7 @@ In the first example, each instance of the template had one parameter, and that
used as a label. However label keys are limited in [what characters they can used as a label. However label keys are limited in [what characters they can
contain](/docs/user-guide/labels/#syntax-and-character-set). contain](/docs/user-guide/labels/#syntax-and-character-set).
This slightly more complex example uses a the jinja2 template language to generate our objects. This slightly more complex example uses the jinja2 template language to generate our objects.
We will use a one-line python script to convert the template to a file. We will use a one-line python script to convert the template to a file.
First, copy and paste the following template of a Job object, into a file called `job.yaml.jinja2`: First, copy and paste the following template of a Job object, into a file called `job.yaml.jinja2`:
@ -179,6 +179,7 @@ cat job.yaml.jinja2 | render_template | kubectl create -f -
## Alternatives ## Alternatives
If you have a large number of job objects, you may find that: If you have a large number of job objects, you may find that:
- even using labels, managing so many Job objects is cumbersome. - even using labels, managing so many Job objects is cumbersome.
- You exceed resource quota when creating all the Jobs at once, - You exceed resource quota when creating all the Jobs at once,
and do not want to wait to create them incrementally. and do not want to wait to create them incrementally.