From 1b16f6679dc4344de681a30164757778e6d9bacf Mon Sep 17 00:00:00 2001 From: ryandawsonuk Date: Wed, 7 Nov 2018 09:43:32 +0000 Subject: [PATCH] fix formatting problem by escaping underscore Signed-off-by: ryandawsonuk --- docs/chart_best_practices/templates.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/chart_best_practices/templates.md b/docs/chart_best_practices/templates.md index 6b8e0d686..8eae99a8c 100644 --- a/docs/chart_best_practices/templates.md +++ b/docs/chart_best_practices/templates.md @@ -73,7 +73,7 @@ Blocks (such as control structures) may be indented to indicate flow of the temp ``` {{ if $foo -}} {{- with .Bar }}Hello{{ end -}} -{{- end -}} +{{- end -}} ``` However, since YAML is a whitespace-oriented language, it is often not possible for code indentation to follow that convention. @@ -145,7 +145,7 @@ metadata: name: {{ .Release.Name }}-myservice ``` -Or if there is only one resource of this kind then we could use .Release.Name or the template fullname function defined in _helpers.tpl (which uses release name): +Or if there is only one resource of this kind then we could use .Release.Name or the template fullname function defined in \_helpers.tpl (which uses release name): ```yaml apiVersion: v1 @@ -217,7 +217,7 @@ readable than other YAML representations. For example, this YAML is closer to the normal YAML method of expressing lists: ```yaml -arguments: +arguments: - "--dirname" - "/foo" ```