From 78e7b40600c292c7d2d3e44634db991506153d38 Mon Sep 17 00:00:00 2001 From: foliage Date: Tue, 27 Dec 2016 22:34:14 +0800 Subject: [PATCH] update jobs-expansions-index.md change the wrong url change the wrong template --- docs/user-guide/jobs/expansions/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/jobs/expansions/index.md b/docs/user-guide/jobs/expansions/index.md index 70eb90a623..c7a7a8b76f 100644 --- a/docs/user-guide/jobs/expansions/index.md +++ b/docs/user-guide/jobs/expansions/index.md @@ -109,7 +109,7 @@ Processing item cherry In the first example, each instance of the template had one parameter, and that parameter was also 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. We will use a one-line python script to convert the template to a file. @@ -128,7 +128,7 @@ First, copy and paste the following template of a Job object, into a file called apiVersion: batch/v1 kind: Job metadata: - name: jobexample-{{ {{ name }} }} + name: jobexample-{{ name }} labels: jobgroup: jobexample spec: