From b983a1499ef3ba6bb1ec93c07cda5d8bc5e3d1fb Mon Sep 17 00:00:00 2001 From: Michael Riedel Date: Mon, 29 Jun 2026 13:01:55 +0200 Subject: [PATCH 01/14] Refactor the YAML techniques appendix. Adjust document structure so that contents about secure YAML templating can be added more easily in the future. Signed-off-by: Michael Riedel --- docs/chart_template_guide/yaml_techniques.md | 133 +++++++++---------- 1 file changed, 65 insertions(+), 68 deletions(-) diff --git a/docs/chart_template_guide/yaml_techniques.md b/docs/chart_template_guide/yaml_techniques.md index b581218bd..262d45eb2 100644 --- a/docs/chart_template_guide/yaml_techniques.md +++ b/docs/chart_template_guide/yaml_techniques.md @@ -9,74 +9,9 @@ we'll look at the YAML format. YAML has some useful features that we, as template authors, can use to make our templates less error prone and easier to read. -## Scalars and Collections +The [YAML specification](https://yaml.org/spec/1.2/spec.html) distinguishes between two kinds of data types: *scalar* types, which represent individual values such as *strings*, *numbers*, *booleans*, and *null*; and *collection* types, which group values together as either *maps* (key–value pairs) or *sequences* (ordered lists). The following sections cover each of these in more depth. -According to the [YAML spec](https://yaml.org/spec/1.2/spec.html), there are two -types of collections, and many scalar types. - -The two types of collections are maps and sequences: - -```yaml -map: - one: 1 - two: 2 - three: 3 - -sequence: - - one - - two - - three -``` - -Scalar values are individual values (as opposed to collections) - -### Scalar Types in YAML - -In Helm's dialect of YAML, the scalar data type of a value is determined by a -complex set of rules, including the Kubernetes schema for resource definitions. -But when inferring types, the following rules tend to hold true. - -If an integer or float is an unquoted bare word, it is typically treated as a -numeric type: - -```yaml -count: 1 -size: 2.34 -``` - -But if they are quoted, they are treated as strings: - -```yaml -count: "1" # <-- string, not int -size: '2.34' # <-- string, not float -``` - -The same is true of booleans: - -```yaml -isGood: true # bool -answer: "true" # string -``` - -The word for an empty value is `null` (not `nil`). - -Note that `port: "80"` is valid YAML, and will pass through both the template -engine and the YAML parser, but will fail if Kubernetes expects `port` to be an -integer. - -In some cases, you can force a particular type inference using YAML node tags: - -```yaml -coffee: "yes, please" -age: !!str 21 -port: !!int "80" -``` - -In the above, `!!str` tells the parser that `age` is a string, even if it looks -like an int. And `port` is treated as an int, even though it is quoted. - - -## Strings in YAML +## YAML Strings Much of the data that we place in YAML documents are strings. YAML has more than one way to represent a string. This section explains the ways and demonstrates @@ -251,6 +186,68 @@ coffee: >- The above will produce `Latte\n 12 oz\n 16 oz\nCappuccino Espresso`. Note that both the spacing and the newlines are still there. +## Other YAML Scalars + +Scalar values are individual values (as opposed to collections). In Helm's +dialect of YAML, the scalar data type of a value is determined by a complex set +of rules, including the Kubernetes schema for resource definitions. But when +inferring types, the following rules tend to hold true. + +If an integer or float is an unquoted bare word, it is typically treated as a +numeric type: + +```yaml +count: 1 +size: 2.34 +``` + +But if they are quoted, they are treated as strings: + +```yaml +count: "1" # <-- string, not int +size: '2.34' # <-- string, not float +``` + +The same is true of booleans: + +```yaml +isGood: true # bool +answer: "true" # string +``` + +The word for an empty value is `null` (not `nil`). + +Note that `port: "80"` is valid YAML, and will pass through both the template +engine and the YAML parser, but will fail if Kubernetes expects `port` to be an +integer. + +In some cases, you can force a particular type inference using YAML node tags: + +```yaml +coffee: "yes, please" +age: !!str 21 +port: !!int "80" +``` + +In the above, `!!str` tells the parser that `age` is a string, even if it looks +like an int. And `port` is treated as an int, even though it is quoted. + +## YAML Collections + +YAML collection types can be used for composing data from other YAML types, be it scalar types or other collections. There are two types of collections: *maps* (key–value pairs) and *sequences* (ordered lists): + +```yaml +map: + one: 1 + two: 2 + three: 3 + +sequence: + - one + - two + - three +``` + ## Embedding Multiple Documents in One File It is possible to place more than one YAML document into a single file. This is @@ -309,7 +306,7 @@ And the two can be mixed (with care): ```yaml coffee: "yes, please" -coffees: [ "Latte", "Cappuccino", "Espresso"] +coffees: [ "Latte", "Cappuccino", "Espresso" ] ``` All three of these should parse into the same internal representation. From 672e58a8de070e95fd090d0bfdc9b281b65ef634 Mon Sep 17 00:00:00 2001 From: Michael Riedel Date: Mon, 29 Jun 2026 17:25:10 +0200 Subject: [PATCH 02/14] Write section about generating YAML strings in templates. Move the existing section about indenting and templates after the new section, because it also generates strings from dynamic values. Also add some TODO markers for other sections. Signed-off-by: Michael Riedel --- docs/chart_template_guide/yaml_techniques.md | 101 ++++++++++++++----- 1 file changed, 77 insertions(+), 24 deletions(-) diff --git a/docs/chart_template_guide/yaml_techniques.md b/docs/chart_template_guide/yaml_techniques.md index 262d45eb2..426461c70 100644 --- a/docs/chart_template_guide/yaml_techniques.md +++ b/docs/chart_template_guide/yaml_techniques.md @@ -128,30 +128,6 @@ coffee: |- In the above case, `coffee` will be `Latte\n 12 oz\n 16 oz\nCappuccino\nEspresso`. -### Indenting and Templates - -When writing templates, you may find yourself wanting to inject the contents of -a file into the template. As we saw in previous chapters, there are two ways of -doing this: - -- Use `{{ .Files.Get "FILENAME" }}` to get the contents of a file in the chart. -- Use `{{ include "TEMPLATE" . }}` to render a template and then place its - contents into the chart. - -When inserting files into YAML, it's good to understand the multi-line rules -above. Often times, the easiest way to insert a static file is to do something -like this: - -```yaml -myfile: | - {{- .Files.Get "myfile.txt" | nindent 2 }} -``` - -Note how we do the indentation above: `nindent 2` tells the template engine to -add a newline and indent every line in "myfile.txt" with two spaces. The `{{-` -trims the whitespace to the left, and `nindent` re-adds the newline with the -correct indentation. - ### Folded Multi-line Strings Sometimes you want to represent a string in your YAML with multiple lines, but @@ -186,6 +162,71 @@ coffee: >- The above will produce `Latte\n 12 oz\n 16 oz\nCappuccino Espresso`. Note that both the spacing and the newlines are still there. +### Generating Strings in Templates + +So far, this section has covered static YAML strings. That is, YAML strings that are copied from the template to the resulting YAML file verbatim. + +Things get more complicated, when templates generate YAML strings based on [dynamic values](/chart_template_guide/values_files.mdx). These values could contain YAML special characters (including line-breaks and indent), so the following naive approach could break the YAML structure that we intend: + +```yaml +data: + drink: {{ .Values.favorite.drink }} +``` + +To address this problem, we can encode values as double-quoted YAML strings using the [`quote`](/chart_template_guide/function_list.mdx#quote-and-squote) function: + +```yaml +data: + drink: {{ .Values.favorite.drink | quote }} +``` + +The `quote` function both wraps the input value in quotes and escapes control characters that have a special meaning within double-quoted YAML strings. This means that we must **not** add our own quotes around the outputs of the `quote` function. + +This also means, that constructing a YAML string from multiple values is slightly more complicated. We can do so, by concatenating the values (using functions such as `print` or `printf`) and then piping the result to `quote`: + +``` +data: + endorsement: {{ print "The " .Release.Name " release loves " .Values.favorite.drink "!" | quote }} + disclaimer: {{ printf "This endorsement is paid for by the %s industry." .Values.favorite.drink | quote }} +``` + +As the YAML spec says, double-quoted strings are "the only style capable of expressing arbitrary strings". However, double-quoted strings can be hard to read, in particular, when they are long and contain line-breaks. In these situations, we can use multi-line strings in flow syntax, as described above. When generating multi-line YAML strings from dynamic values, it is important to get the indent right. For this, we can use the `nindent` function in our template: + +```yaml +myLongText: | + {{- .Values.stringWithLongText | nindent 2 }} +``` + +Note how we do the indentation above: `nindent 2` tells the template engine to +add a newline and indent every line in `stringWithLongText` with two spaces. The `{{-` +trims the whitespace to the left, and `nindent` re-adds the newline with the +correct indentation. + +As noted above, there is one caveat to this approach. If the first non-blank line of the value contains leading white-space this breaks our indent. +The YAML parser will report this as an error and Helm will abort the install or update. When this happens we should adjust our template and generate the YAML string for this value using the `quote` function instead. + +### Importing Files into Strings in Templates + +When writing templates, you may find yourself wanting to inject the contents of +a file into the template. As we saw in previous chapters, there are two ways of +doing this: + +- Use `{{ .Files.Get "FILENAME" }}` to get the contents of a file in the chart. +- Use `{{ include "TEMPLATE" . }}` to render a template and then place its + contents into the chart. + +When inserting files into YAML strings, it's good to understand the encoding rules +above. We can use either the `quote` approach or the `nindent` approach: + +```yaml +myfile: + {{ .Files.Get "myfile.txt" | quote }} +mytemplate: | + {{- include "mytemplate.txt" . | nindent 2 }} +``` + +Obviously this also works the other way round, using `.Files.Get` with `nindent` and using `include` with `quote`. + ## Other YAML Scalars Scalar values are individual values (as opposed to collections). In Helm's @@ -232,6 +273,10 @@ port: !!int "80" In the above, `!!str` tells the parser that `age` is a string, even if it looks like an int. And `port` is treated as an int, even though it is quoted. +### Generating Scalars in Templates + +TODO + ## YAML Collections YAML collection types can be used for composing data from other YAML types, be it scalar types or other collections. There are two types of collections: *maps* (key–value pairs) and *sequences* (ordered lists): @@ -248,6 +293,10 @@ sequence: - three ``` +### Generating Collections in Templates + +TODO + ## Embedding Multiple Documents in One File It is possible to place more than one YAML document into a single file. This is @@ -350,3 +399,7 @@ coffees: Because Helm and Kubernetes often read, modify, and then rewrite YAML files, the anchors will be lost. + +## Security Considerations + +TODO From d96bf10fcb10ae5b92c3c2cadea99d05c163d4b2 Mon Sep 17 00:00:00 2001 From: Michael Riedel Date: Mon, 29 Jun 2026 21:10:06 +0200 Subject: [PATCH 03/14] Fix line folding. Signed-off-by: Michael Riedel --- docs/chart_template_guide/yaml_techniques.md | 58 +++++++++++++++----- 1 file changed, 43 insertions(+), 15 deletions(-) diff --git a/docs/chart_template_guide/yaml_techniques.md b/docs/chart_template_guide/yaml_techniques.md index 426461c70..fea7de01a 100644 --- a/docs/chart_template_guide/yaml_techniques.md +++ b/docs/chart_template_guide/yaml_techniques.md @@ -9,7 +9,12 @@ we'll look at the YAML format. YAML has some useful features that we, as template authors, can use to make our templates less error prone and easier to read. -The [YAML specification](https://yaml.org/spec/1.2/spec.html) distinguishes between two kinds of data types: *scalar* types, which represent individual values such as *strings*, *numbers*, *booleans*, and *null*; and *collection* types, which group values together as either *maps* (key–value pairs) or *sequences* (ordered lists). The following sections cover each of these in more depth. +The [YAML specification](https://yaml.org/spec/1.2/spec.html) distinguishes +between two kinds of data types: *scalar* types, which represent individual +values such as *strings*, *numbers*, *booleans*, and *null*; and *collection* +types, which group values together as either *maps* (key–value pairs) or +*sequences* (ordered lists). The following sections cover each of these in +more depth. ## YAML Strings @@ -164,25 +169,36 @@ both the spacing and the newlines are still there. ### Generating Strings in Templates -So far, this section has covered static YAML strings. That is, YAML strings that are copied from the template to the resulting YAML file verbatim. +So far, this section has covered static YAML strings. That is, YAML strings +that are copied from the template to the resulting YAML file verbatim. -Things get more complicated, when templates generate YAML strings based on [dynamic values](/chart_template_guide/values_files.mdx). These values could contain YAML special characters (including line-breaks and indent), so the following naive approach could break the YAML structure that we intend: +Things get more complicated, when templates generate YAML strings based on +[dynamic values](/chart_template_guide/values_files.mdx). These values could +contain YAML special characters (including line-breaks and indent), so the +following naive approach could break the YAML structure that we intend: ```yaml data: drink: {{ .Values.favorite.drink }} ``` -To address this problem, we can encode values as double-quoted YAML strings using the [`quote`](/chart_template_guide/function_list.mdx#quote-and-squote) function: +To address this problem, we can encode values as double-quoted YAML strings +using the [`quote`](/chart_template_guide/function_list.mdx#quote-and-squote) +function: ```yaml data: drink: {{ .Values.favorite.drink | quote }} ``` -The `quote` function both wraps the input value in quotes and escapes control characters that have a special meaning within double-quoted YAML strings. This means that we must **not** add our own quotes around the outputs of the `quote` function. +The `quote` function both wraps the input value in quotes and escapes control +characters that have a special meaning within double-quoted YAML strings. +This means that we must **not** add our own quotes around the outputs of the +`quote` function. -This also means, that constructing a YAML string from multiple values is slightly more complicated. We can do so, by concatenating the values (using functions such as `print` or `printf`) and then piping the result to `quote`: +This also means, that constructing a YAML string from multiple values is +slightly more complicated. We can do so, by concatenating the values (using +functions such as `print` or `printf`) and then piping the result to `quote`: ``` data: @@ -190,7 +206,13 @@ data: disclaimer: {{ printf "This endorsement is paid for by the %s industry." .Values.favorite.drink | quote }} ``` -As the YAML spec says, double-quoted strings are "the only style capable of expressing arbitrary strings". However, double-quoted strings can be hard to read, in particular, when they are long and contain line-breaks. In these situations, we can use multi-line strings in flow syntax, as described above. When generating multi-line YAML strings from dynamic values, it is important to get the indent right. For this, we can use the `nindent` function in our template: +As the YAML spec says, double-quoted strings are "the only style capable of +expressing arbitrary strings". However, double-quoted strings can be hard to +read, in particular, when they are long and contain line-breaks. In these +situations, we can use multi-line strings in flow syntax, as described above. +When generating multi-line YAML strings from dynamic values, it is important +to get the indent right. For this, we can use the `nindent` function in our +template: ```yaml myLongText: | @@ -198,12 +220,15 @@ myLongText: | ``` Note how we do the indentation above: `nindent 2` tells the template engine to -add a newline and indent every line in `stringWithLongText` with two spaces. The `{{-` -trims the whitespace to the left, and `nindent` re-adds the newline with the +add a newline and indent every line in `stringWithLongText` with two spaces. +The `{{-` trims the whitespace to the left, and `nindent` re-adds the newline correct indentation. -As noted above, there is one caveat to this approach. If the first non-blank line of the value contains leading white-space this breaks our indent. -The YAML parser will report this as an error and Helm will abort the install or update. When this happens we should adjust our template and generate the YAML string for this value using the `quote` function instead. +As noted above, there is one caveat to this approach. If the first non-blank +line of the value contains leading white-space this breaks our indent. +The YAML parser will report this as an error and Helm will abort the install +or update. When this happens we should adjust our template and generate the +YAML string for this value using the `quote` function instead. ### Importing Files into Strings in Templates @@ -215,8 +240,8 @@ doing this: - Use `{{ include "TEMPLATE" . }}` to render a template and then place its contents into the chart. -When inserting files into YAML strings, it's good to understand the encoding rules -above. We can use either the `quote` approach or the `nindent` approach: +When inserting files into YAML strings, it's good to understand the encoding +rules above. We can use either the `quote` approach or the `nindent` approach: ```yaml myfile: @@ -225,7 +250,8 @@ mytemplate: | {{- include "mytemplate.txt" . | nindent 2 }} ``` -Obviously this also works the other way round, using `.Files.Get` with `nindent` and using `include` with `quote`. +Obviously this also works the other way round, using `.Files.Get` with +`nindent` and using `include` with `quote`. ## Other YAML Scalars @@ -279,7 +305,9 @@ TODO ## YAML Collections -YAML collection types can be used for composing data from other YAML types, be it scalar types or other collections. There are two types of collections: *maps* (key–value pairs) and *sequences* (ordered lists): +YAML collection types can be used for composing data from other YAML types, +be it scalar types or other collections. There are two types of collections: +*maps* (key–value pairs) and *sequences* (ordered lists): ```yaml map: From 28455bf91e26f19d832655348b3203885f2f1610 Mon Sep 17 00:00:00 2001 From: Michael Riedel Date: Tue, 30 Jun 2026 21:52:31 +0200 Subject: [PATCH 04/14] Write section about non-string YAML scalars. Signed-off-by: Michael Riedel --- docs/chart_template_guide/yaml_techniques.md | 47 ++++++++++++++++++-- 1 file changed, 43 insertions(+), 4 deletions(-) diff --git a/docs/chart_template_guide/yaml_techniques.md b/docs/chart_template_guide/yaml_techniques.md index fea7de01a..9f0dbe59c 100644 --- a/docs/chart_template_guide/yaml_techniques.md +++ b/docs/chart_template_guide/yaml_techniques.md @@ -255,9 +255,10 @@ Obviously this also works the other way round, using `.Files.Get` with ## Other YAML Scalars -Scalar values are individual values (as opposed to collections). In Helm's -dialect of YAML, the scalar data type of a value is determined by a complex set -of rules, including the Kubernetes schema for resource definitions. But when +Strings are a common type of YAML scalars, but not the only one. Other scalar +types include *integers*, *floats*, *booleans*, and *null*. In Helm's dialect +of YAML, the scalar data type of a value is determined by a complex set of +rules, including the Kubernetes schema for resource definitions. But when inferring types, the following rules tend to hold true. If an integer or float is an unquoted bare word, it is typically treated as a @@ -293,7 +294,10 @@ In some cases, you can force a particular type inference using YAML node tags: ```yaml coffee: "yes, please" age: !!str 21 +pi: !!float "3.14" port: !!int "80" +enable: !!bool "false" +extras: !!null "null" ``` In the above, `!!str` tells the parser that `age` is a string, even if it looks @@ -301,7 +305,42 @@ like an int. And `port` is treated as an int, even though it is quoted. ### Generating Scalars in Templates -TODO +So far, we have covered static YAML scalars. That is, YAML scalars +that are copied from the template to the resulting YAML file verbatim. + +In an ideal case, generating non-string YAML scalars based on +[dynamic values](/chart_template_guide/values_files.mdx) does not require +special attention. Templates serialize +[Go Data Types](/chart_template_guide/data_types.mdx) in a manner that is +compatible with YAML. A string value that holds the representation of a number, +boolean, or null can also be emitted into a YAML file verbatim. No extra +quoting or escaping is needed in any of these situations. + +However, there is a catch: as Helm template authors we can never be certain +about the dynamic values that users will pass to our Helm chart. Therefore, it +is preferable to add explicit type constraints whenever emitting dynamic values +as non-string scalars. As seen in the previous sub-section, we can use YAML +node tags to achieve this: + +```yaml +pi: !!float {{ .Values.constants.pi | quote }} +port: !!int {{ .Values.service.port | quote }} +enable: !!bool {{ .Values.service.enable | quote }} +``` + +In the above, the Go template code treats all scalars as it would treat +strings: it wraps them in double-quotes and escapes special characters. Then, +the YAML node tags tell the YAML parser to convert this string scalar to the +desired YAML type (e.g. a floating point number, an integer number, or a +boolean). + +If the string contents do not match the expected YAML scalar type, Helm's YAML +parser will report an error even before Helm even passes the YAML data to +Kubernetes. This fail-fast approach can make debugging much easier, when users +pass an unexpected value to the Helm chart. E.g. when a dynamic value is not +the expected integer, but a string containing YAML special characters (such as +quotation marks, colons, brackets, curly braces, line-breaks, etc.) this can +prevent debugging nightmares. ## YAML Collections From 6c3af0301840f193e88be009fa7a489a529bf81e Mon Sep 17 00:00:00 2001 From: Michael Riedel Date: Thu, 2 Jul 2026 12:35:43 +0200 Subject: [PATCH 05/14] Write section about generating YAML collections. Also improve text and formatting in a few related sections. And add more specific TODOs. Signed-off-by: Michael Riedel --- docs/chart_template_guide/yaml_techniques.md | 69 +++++++++++++++++--- 1 file changed, 59 insertions(+), 10 deletions(-) diff --git a/docs/chart_template_guide/yaml_techniques.md b/docs/chart_template_guide/yaml_techniques.md index 9f0dbe59c..3f2dc37e8 100644 --- a/docs/chart_template_guide/yaml_techniques.md +++ b/docs/chart_template_guide/yaml_techniques.md @@ -200,7 +200,7 @@ This also means, that constructing a YAML string from multiple values is slightly more complicated. We can do so, by concatenating the values (using functions such as `print` or `printf`) and then piping the result to `quote`: -``` +```yaml data: endorsement: {{ print "The " .Release.Name " release loves " .Values.favorite.drink "!" | quote }} disclaimer: {{ printf "This endorsement is paid for by the %s industry." .Values.favorite.drink | quote }} @@ -211,7 +211,8 @@ expressing arbitrary strings". However, double-quoted strings can be hard to read, in particular, when they are long and contain line-breaks. In these situations, we can use multi-line strings in flow syntax, as described above. When generating multi-line YAML strings from dynamic values, it is important -to get the indent right. For this, we can use the `nindent` function in our +to get the indent right. For this, we can use the +[`nindent`](/chart_template_guide/function_list/#nindent) function in our template: ```yaml @@ -222,13 +223,20 @@ myLongText: | Note how we do the indentation above: `nindent 2` tells the template engine to add a newline and indent every line in `stringWithLongText` with two spaces. The `{{-` trims the whitespace to the left, and `nindent` re-adds the newline -correct indentation. +and correct indentation. -As noted above, there is one caveat to this approach. If the first non-blank -line of the value contains leading white-space this breaks our indent. -The YAML parser will report this as an error and Helm will abort the install -or update. When this happens we should adjust our template and generate the -YAML string for this value using the `quote` function instead. +As noted for static case, there is a caveat to this approach. If the first +non-blank line of the value contains leading white-space this breaks our +indent. The YAML parser will report this as an error and Helm will abort the +install or update. When this happens we can adjust our template and generate +the YAML string for this value using the `quote` function instead. + +Another catch is that the `nindent` value must be greater than the indent of +the surrounding YAML. In the above example, `myLongText` has zero indent, so we +use `nindent 2`. If `myLongText` had an indent of 4, we'd use `nindent 6` +instead. It is customary to increase indent in steps of `2`. When changing the +indent of surrounding YAML, take care to adjust relevant `nindent` values +accordingly! ### Importing Files into Strings in Templates @@ -362,7 +370,46 @@ sequence: ### Generating Collections in Templates -TODO +Now let's look how we can generate YAML collection types based on dynamic +values. We can do by combining +[`toYaml`](/chart_template_guide/function_list/#toyaml-toyamlpretty) function +and the [`nindent`](/chart_template_guide/function_list/#nindent) function: + +```yaml +map: + {{- toYaml .Values.myMap | nindent 2 }} + +sequence: + {{- toYaml .Values.mySequence | nindent 2 }} +``` + +Note how we do the indentation above: `nindent 2` tells the template engine to +add a newline and indent every line in `stringWithLongText` with two spaces. +The `{{-` trims the whitespace to the left, and `nindent` re-adds the newline +and correct indentation. + +Note that in the above, the template code is identical for both the map and the +sequence. The `toYaml` method determines the YAML type to generate by the +[Go Data Type](/chart_template_guide/data_types.mdx) od the dynamic value. + +If the dynamic value originates from a `values.yaml` file, the original YAML +type of the value will be preserved. This also works reliably for nested YAML +collections and YAML scalars, too. Therefore, the above is a good method for +copying larger chunks of data from dynamic values to the YAML file generated by +the template. + +Incidently, the above `toYaml`/`nindent` approach works not just for YAML +collections, but also for YAML scalars (including strings). So you can safely +use it for dynamic values of any YAML type. This is particularly useful in +situations where template authors do not want to restrict the YAML type of a +value that users will ultimately feed to the Helm chart. That said, dedicated +YAML encoding techniques for scalars (as introduced further above) are often +more concise and more readable. + +As always when using `nindent` to generate YAML, it is important to the the +`nindent` value right. The `nindent` must be greater than the indent of +surrounding YAML. When changing the indent of surrounding YAML, take care to +adjust relevant `nindent` values accordingly! ## Embedding Multiple Documents in One File @@ -469,4 +516,6 @@ anchors will be lost. ## Security Considerations -TODO +TODO why it matters +TODO get the indent right! +TODO validation schemas and validation in the template are complementary measures. From d32cd2d298d4856658d1399b3d1371db1fe01b6c Mon Sep 17 00:00:00 2001 From: Michael Riedel Date: Thu, 2 Jul 2026 23:11:51 +0200 Subject: [PATCH 06/14] Add contents to the Security Considerations section. Signed-off-by: Michael Riedel --- docs/chart_template_guide/yaml_techniques.md | 110 ++++++++++++++++++- 1 file changed, 107 insertions(+), 3 deletions(-) diff --git a/docs/chart_template_guide/yaml_techniques.md b/docs/chart_template_guide/yaml_techniques.md index 3f2dc37e8..cf1764532 100644 --- a/docs/chart_template_guide/yaml_techniques.md +++ b/docs/chart_template_guide/yaml_techniques.md @@ -516,6 +516,110 @@ anchors will be lost. ## Security Considerations -TODO why it matters -TODO get the indent right! -TODO validation schemas and validation in the template are complementary measures. +The YAML techniques presented in this page, help Helm Chart authors in writing +reliable YAML templates. By applying apropriate encoding techniques when +generating YAML based on dynamic values, template authors can ensure that the +resulting YAML is correct and has the desired structure regardless of what +values users pass to the Helm chart. This ensures functional correctness in all +corner-cases and prevents errors that might be hard to debug. + +However, comprehensive YAML encoding also prevents vulnerabilities that YAML +templates might introduce otherwise. + +### Preventing YAML Injection + +An [injection flaw](https://owasp.org/www-community/Injection_Flaws) is a +vulnerability that allows attackers to inject malicious data or code into a +system. Thus, a YAML injection vulnerabilities allows attackers to inject +malicious data into the YAML file that a template generates. + +YAML code is hardly malicious in itself, but in the context of Helm charts, +YAML is used to control Kubernetes resources. Therefore, attackers could +exploit a YAML injection vulnerability to deploy malicious Kubernetes resources +into your cluster. For example, attackers could: + +* Create pods based on attacker-controlled container images. +* Inject secrets into such containers and leak them over the network. +* Run attacker-controlled commands in existing containers. +* Create new Service Accounts, (Cluster)Roles, and (Cluster)RoleBindings to escalate their privileges. + +In order to run a YAML injection attack, an attacker would first need to pass +their own [values](/chart_template_guide/values_files) to your Helm chart. This +seems unlikely, and in fact it may never happen when you're using your own Helm +charts. Even when consuming Helm charts from other authors, Helm users will +often have full control of the values that they use. + +However, in some *Infrastructure-as-Code* scenarios, users will not pass values +to a Helm chart manually through CLI arguments or value files. Instead, users +may use some orchestration tool (e.g. a CI/CD pipeline) to install Helm charts +and pass values to them. In some scenarios, such orchestration tools may draw +values from additional data-sources that might contain all sorts of data. And +this is where things can get potentially dangerous. + +Here's the good news though: when following the YAML techniques that this page +describes, you're already preventing YAML injection vulnerabilities. It takes +nothing more than applying the described indenting, quoting, and encoding +techniques in your template. When writing your YAML templates in this manner +you and all consumers of your Helm chart are safe from YAML injection. + +### Preventing Dangerous YAML through Validation + +In some situations, additional validation of the dynamic values that a YAML +template processes may be desirable. Usually, the concern here is not the +structure of the resulting YAML, but application specific constraints on the +resources that the Helm chart manages. + +For example, a config map may hold individual fields that must match a certain +format, regardless of how their value is encoded in YAML. This could be the +format of a domain name, an IP address, an email-address, or a URL. In the +latter case, additional constraints regarding the URL scheme may be desirable. + +Helm charts offer two complementary mechanism that help imposing constraints on +dynamic values, *Schematized Values Files* and *Validation Logic in Templates*. + +#### Schema Files + +Helm's [Schema Files](/topics/charts#schema-files) allow chart authors to +validate values against a [JSON Schema](https://json-schema.org/) +(`valuesschema.yaml`). If the user of a Helm chart tries passing dynamic values +to the chart that violate the JSON Schema, Helm reports an error. + +This validation approach is input-centric, as the JSON Schema constrains all +values as passed to the Helm chart. This is useful for values that appear +inside multiple YAML templates of a Helm chart. + +JSON Schema is quite powerful, and can be used to impose validation constraints +on both YAML collections and YAML scalars. For instance, JSON Schema can +validate strings against regular expressions and validate numbers against +ranges. However, more complex validation logic may be hard or impossible to +express in JSON Schema. + +#### Validation Logic in Templates + +Helm chart templates are based on +[Go Templates](https://pkg.go.dev/text/template), which is a powerful template +language that can execute arbitrary program logic. Therefore, complex +validation can be expressed through conditional logic in the YAML template +itself. If validation fails, your template can call the +[fail](/chart_template_guide/function_list#fail) function, which tells Helm to +abort processing the chart with an error. + +For instance, the following YAML template snippet can be used to set a virtual +server's domain name, only if the given value matches a DNS domain: + +```yaml +{{ if not ( regexMatch "^([-a-z0-9]+[.])*([-a-z0-9]+)$" .Values.server.domain ) }} + {{ print "Server domain \"" .Values.server.domain "\" does not look like a valid DNS domain." | fail }} +{{ end }} +server: + port: !!int {{ .Values.server.port | quote }} + domain: {{ .Values.server.domain | quote }} +``` + +(The above is an example only, as it uses a regular expression that does not +enforce all formal requirements for a valid DNS domain.) + +This validation approach is output-centric, as it applies the validation logic +close to where the output is generated. This is useful for values that are +dynamically derived from other values in the template itself. That said, overly +complex processing logic should generally be avoided in templates. From cce6779db0aee9808be2917f988a5a163f8cd523 Mon Sep 17 00:00:00 2001 From: Michael Riedel Date: Fri, 3 Jul 2026 12:06:27 +0200 Subject: [PATCH 07/14] Fix spelling, grammar and consistency issues. Signed-off-by: Michael Riedel --- docs/chart_template_guide/yaml_techniques.md | 60 ++++++++++---------- 1 file changed, 30 insertions(+), 30 deletions(-) diff --git a/docs/chart_template_guide/yaml_techniques.md b/docs/chart_template_guide/yaml_techniques.md index cf1764532..709e1a5ec 100644 --- a/docs/chart_template_guide/yaml_techniques.md +++ b/docs/chart_template_guide/yaml_techniques.md @@ -40,7 +40,7 @@ All inline styles must be on one line. characters. The only escape sequence is `''`, which is decoded as a single `'`. -In addition to the one-line strings, you can declare multi-line strings: +In addition to inline strings, you can declare multi-line strings: ```yaml coffee: | @@ -172,9 +172,9 @@ both the spacing and the newlines are still there. So far, this section has covered static YAML strings. That is, YAML strings that are copied from the template to the resulting YAML file verbatim. -Things get more complicated, when templates generate YAML strings based on +Things get more complicated when templates generate YAML strings based on [dynamic values](/chart_template_guide/values_files.mdx). These values could -contain YAML special characters (including line-breaks and indent), so the +contain YAML special characters (including line breaks and indentation), so the following naive approach could break the YAML structure that we intend: ```yaml @@ -196,8 +196,8 @@ characters that have a special meaning within double-quoted YAML strings. This means that we must **not** add our own quotes around the outputs of the `quote` function. -This also means, that constructing a YAML string from multiple values is -slightly more complicated. We can do so, by concatenating the values (using +This also means that constructing a YAML string from multiple values is +slightly more complicated. We can do so by concatenating the values (using functions such as `print` or `printf`) and then piping the result to `quote`: ```yaml @@ -208,8 +208,8 @@ data: As the YAML spec says, double-quoted strings are "the only style capable of expressing arbitrary strings". However, double-quoted strings can be hard to -read, in particular, when they are long and contain line-breaks. In these -situations, we can use multi-line strings in flow syntax, as described above. +read, in particular, when they are long and contain line breaks. In these +situations, we can use multi-line strings in block syntax, as described above. When generating multi-line YAML strings from dynamic values, it is important to get the indent right. For this, we can use the [`nindent`](/chart_template_guide/function_list/#nindent) function in our @@ -258,7 +258,7 @@ mytemplate: | {{- include "mytemplate.txt" . | nindent 2 }} ``` -Obviously this also works the other way round, using `.Files.Get` with +Obviously this also works the other way around, using `.Files.Get` with `nindent` and using `include` with `quote`. ## Other YAML Scalars @@ -324,10 +324,10 @@ compatible with YAML. A string value that holds the representation of a number, boolean, or null can also be emitted into a YAML file verbatim. No extra quoting or escaping is needed in any of these situations. -However, there is a catch: as Helm template authors we can never be certain +However, there is a catch: as Helm template authors, we can never be certain about the dynamic values that users will pass to our Helm chart. Therefore, it is preferable to add explicit type constraints whenever emitting dynamic values -as non-string scalars. As seen in the previous sub-section, we can use YAML +as non-string scalars. As seen in the previous subsection, we can use YAML node tags to achieve this: ```yaml @@ -343,8 +343,8 @@ desired YAML type (e.g. a floating point number, an integer number, or a boolean). If the string contents do not match the expected YAML scalar type, Helm's YAML -parser will report an error even before Helm even passes the YAML data to -Kubernetes. This fail-fast approach can make debugging much easier, when users +parser will report an error even before Helm passes the YAML data to +Kubernetes. This fail-fast approach can make debugging much easier when users pass an unexpected value to the Helm chart. E.g. when a dynamic value is not the expected integer, but a string containing YAML special characters (such as quotation marks, colons, brackets, curly braces, line-breaks, etc.) this can @@ -370,8 +370,8 @@ sequence: ### Generating Collections in Templates -Now let's look how we can generate YAML collection types based on dynamic -values. We can do by combining +Now let's look at how we can generate YAML collection types based on dynamic +values. We can do so by combining [`toYaml`](/chart_template_guide/function_list/#toyaml-toyamlpretty) function and the [`nindent`](/chart_template_guide/function_list/#nindent) function: @@ -384,21 +384,21 @@ sequence: ``` Note how we do the indentation above: `nindent 2` tells the template engine to -add a newline and indent every line in `stringWithLongText` with two spaces. -The `{{-` trims the whitespace to the left, and `nindent` re-adds the newline -and correct indentation. +add a newline and indent every line of the serialized collection with two +spaces. The `{{-` trims the whitespace to the left, and `nindent` re-adds the +newline and correct indentation. Note that in the above, the template code is identical for both the map and the sequence. The `toYaml` method determines the YAML type to generate by the -[Go Data Type](/chart_template_guide/data_types.mdx) od the dynamic value. +[Go Data Type](/chart_template_guide/data_types.mdx) of the dynamic value. -If the dynamic value originates from a `values.yaml` file, the original YAML +If the dynamic value originates from a `values.yaml` file, the original YAML type of the value will be preserved. This also works reliably for nested YAML collections and YAML scalars, too. Therefore, the above is a good method for copying larger chunks of data from dynamic values to the YAML file generated by the template. -Incidently, the above `toYaml`/`nindent` approach works not just for YAML +Incidentally, the above `toYaml`/`nindent` approach works not just for YAML collections, but also for YAML scalars (including strings). So you can safely use it for dynamic values of any YAML type. This is particularly useful in situations where template authors do not want to restrict the YAML type of a @@ -406,7 +406,7 @@ value that users will ultimately feed to the Helm chart. That said, dedicated YAML encoding techniques for scalars (as introduced further above) are often more concise and more readable. -As always when using `nindent` to generate YAML, it is important to the the +As always when using `nindent` to generate YAML, it is important to get the `nindent` value right. The `nindent` must be greater than the indent of surrounding YAML. When changing the indent of surrounding YAML, take care to adjust relevant `nindent` values accordingly! @@ -516,21 +516,21 @@ anchors will be lost. ## Security Considerations -The YAML techniques presented in this page, help Helm Chart authors in writing -reliable YAML templates. By applying apropriate encoding techniques when +The YAML techniques presented in this page help Helm chart authors in writing +reliable YAML templates. By applying appropriate encoding techniques when generating YAML based on dynamic values, template authors can ensure that the resulting YAML is correct and has the desired structure regardless of what values users pass to the Helm chart. This ensures functional correctness in all corner-cases and prevents errors that might be hard to debug. However, comprehensive YAML encoding also prevents vulnerabilities that YAML -templates might introduce otherwise. +templates might otherwise introduce. ### Preventing YAML Injection An [injection flaw](https://owasp.org/www-community/Injection_Flaws) is a vulnerability that allows attackers to inject malicious data or code into a -system. Thus, a YAML injection vulnerabilities allows attackers to inject +system. Thus, a YAML injection vulnerability allows attackers to inject malicious data into the YAML file that a template generates. YAML code is hardly malicious in itself, but in the context of Helm charts, @@ -553,7 +553,7 @@ However, in some *Infrastructure-as-Code* scenarios, users will not pass values to a Helm chart manually through CLI arguments or value files. Instead, users may use some orchestration tool (e.g. a CI/CD pipeline) to install Helm charts and pass values to them. In some scenarios, such orchestration tools may draw -values from additional data-sources that might contain all sorts of data. And +values from additional data sources that might contain all sorts of data. And this is where things can get potentially dangerous. Here's the good news though: when following the YAML techniques that this page @@ -574,14 +574,14 @@ format, regardless of how their value is encoded in YAML. This could be the format of a domain name, an IP address, an email-address, or a URL. In the latter case, additional constraints regarding the URL scheme may be desirable. -Helm charts offer two complementary mechanism that help imposing constraints on -dynamic values, *Schematized Values Files* and *Validation Logic in Templates*. +Helm charts offer two complementary mechanisms that help impose constraints on +dynamic values, *Schema Files* and *Validation Logic in Templates*. #### Schema Files Helm's [Schema Files](/topics/charts#schema-files) allow chart authors to validate values against a [JSON Schema](https://json-schema.org/) -(`valuesschema.yaml`). If the user of a Helm chart tries passing dynamic values +(`values.schema.json`). If the user of a Helm chart tries to pass dynamic values to the chart that violate the JSON Schema, Helm reports an error. This validation approach is input-centric, as the JSON Schema constrains all @@ -605,7 +605,7 @@ itself. If validation fails, your template can call the abort processing the chart with an error. For instance, the following YAML template snippet can be used to set a virtual -server's domain name, only if the given value matches a DNS domain: +server's domain name only if the given value matches a DNS domain: ```yaml {{ if not ( regexMatch "^([-a-z0-9]+[.])*([-a-z0-9]+)$" .Values.server.domain ) }} From ee10cf771c7f22e34e03d7116d6bfb48f89bac88 Mon Sep 17 00:00:00 2001 From: Michael Riedel Date: Fri, 3 Jul 2026 12:35:22 +0200 Subject: [PATCH 08/14] Make text and code-sample more consistent. Signed-off-by: Michael Riedel --- docs/chart_template_guide/yaml_techniques.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/chart_template_guide/yaml_techniques.md b/docs/chart_template_guide/yaml_techniques.md index 709e1a5ec..65dea6460 100644 --- a/docs/chart_template_guide/yaml_techniques.md +++ b/docs/chart_template_guide/yaml_techniques.md @@ -300,7 +300,6 @@ integer. In some cases, you can force a particular type inference using YAML node tags: ```yaml -coffee: "yes, please" age: !!str 21 pi: !!float "3.14" port: !!int "80" @@ -308,8 +307,10 @@ enable: !!bool "false" extras: !!null "null" ``` -In the above, `!!str` tells the parser that `age` is a string, even if it looks -like an int. And `port` is treated as an int, even though it is quoted. +In the above, `!!str` tells the parser that `age` is a string, even though its +value looks like an integer. And the tags for `pi`, `port`, `enable`, and +`extras` tell the parser that these are float, integer, boolean, and null +values respectively, even though they are quoted. ### Generating Scalars in Templates From 382d659378422ed3a2f83127d71755db1c009aff Mon Sep 17 00:00:00 2001 From: Michael Riedel Date: Fri, 3 Jul 2026 18:00:35 +0200 Subject: [PATCH 09/14] Refine text regarding validation. Signed-off-by: Michael Riedel --- docs/chart_template_guide/yaml_techniques.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/docs/chart_template_guide/yaml_techniques.md b/docs/chart_template_guide/yaml_techniques.md index 65dea6460..f36878f35 100644 --- a/docs/chart_template_guide/yaml_techniques.md +++ b/docs/chart_template_guide/yaml_techniques.md @@ -617,10 +617,17 @@ server: domain: {{ .Values.server.domain | quote }} ``` -(The above is an example only, as it uses a regular expression that does not -enforce all formal requirements for a valid DNS domain.) +(The above is an example only, as the regular expression does not enforce all +formal requirements for a valid DNS domain.) This validation approach is output-centric, as it applies the validation logic -close to where the output is generated. This is useful for values that are +close to where the YAML output is generated. This is useful for values that are dynamically derived from other values in the template itself. That said, overly complex processing logic should generally be avoided in templates. + +Note that the above example still encodes the `domain` value using the `quote` +function. This is not strictly necessary here, because validation blocks all +values that would require YAML encoding and quoting. However, the use of +`quote` makes the template more robust with respect to future changes. It is +also cleaner conceptually, since ensuring a valid domain and producing correct +YAML are two separate concerns. \ No newline at end of file From d17b87fefa30fe925da8a12e96c845c04eb550fb Mon Sep 17 00:00:00 2001 From: Michael Riedel Date: Fri, 3 Jul 2026 21:25:10 +0200 Subject: [PATCH 10/14] Fix broken links. Signed-off-by: Michael Riedel --- docs/chart_template_guide/yaml_techniques.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/chart_template_guide/yaml_techniques.md b/docs/chart_template_guide/yaml_techniques.md index f36878f35..eba26e4a9 100644 --- a/docs/chart_template_guide/yaml_techniques.md +++ b/docs/chart_template_guide/yaml_techniques.md @@ -212,7 +212,7 @@ read, in particular, when they are long and contain line breaks. In these situations, we can use multi-line strings in block syntax, as described above. When generating multi-line YAML strings from dynamic values, it is important to get the indent right. For this, we can use the -[`nindent`](/chart_template_guide/function_list/#nindent) function in our +[`nindent`](/chart_template_guide/function_list.mdx#nindent) function in our template: ```yaml @@ -255,7 +255,7 @@ rules above. We can use either the `quote` approach or the `nindent` approach: myfile: {{ .Files.Get "myfile.txt" | quote }} mytemplate: | - {{- include "mytemplate.txt" . | nindent 2 }} + {{- include "mytemplate" . | nindent 2 }} ``` Obviously this also works the other way around, using `.Files.Get` with @@ -320,7 +320,7 @@ that are copied from the template to the resulting YAML file verbatim. In an ideal case, generating non-string YAML scalars based on [dynamic values](/chart_template_guide/values_files.mdx) does not require special attention. Templates serialize -[Go Data Types](/chart_template_guide/data_types.mdx) in a manner that is +[Go Data Types](/chart_template_guide/data_types.md) in a manner that is compatible with YAML. A string value that holds the representation of a number, boolean, or null can also be emitted into a YAML file verbatim. No extra quoting or escaping is needed in any of these situations. @@ -373,8 +373,8 @@ sequence: Now let's look at how we can generate YAML collection types based on dynamic values. We can do so by combining -[`toYaml`](/chart_template_guide/function_list/#toyaml-toyamlpretty) function -and the [`nindent`](/chart_template_guide/function_list/#nindent) function: +[`toYaml`](/chart_template_guide/function_list.mdx#toyaml-toyamlpretty) function +and the [`nindent`](/chart_template_guide/function_list.mdx#nindent) function: ```yaml map: @@ -391,7 +391,7 @@ newline and correct indentation. Note that in the above, the template code is identical for both the map and the sequence. The `toYaml` method determines the YAML type to generate by the -[Go Data Type](/chart_template_guide/data_types.mdx) of the dynamic value. +[Go Data Type](/chart_template_guide/data_types.md) of the dynamic value. If the dynamic value originates from a `values.yaml` file, the original YAML type of the value will be preserved. This also works reliably for nested YAML @@ -545,7 +545,7 @@ into your cluster. For example, attackers could: * Create new Service Accounts, (Cluster)Roles, and (Cluster)RoleBindings to escalate their privileges. In order to run a YAML injection attack, an attacker would first need to pass -their own [values](/chart_template_guide/values_files) to your Helm chart. This +their own [values](/chart_template_guide/values_files.mdx) to your Helm chart. This seems unlikely, and in fact it may never happen when you're using your own Helm charts. Even when consuming Helm charts from other authors, Helm users will often have full control of the values that they use. @@ -580,7 +580,7 @@ dynamic values, *Schema Files* and *Validation Logic in Templates*. #### Schema Files -Helm's [Schema Files](/topics/charts#schema-files) allow chart authors to +Helm's [Schema Files](/topics/charts.mdx#schema-files) allow chart authors to validate values against a [JSON Schema](https://json-schema.org/) (`values.schema.json`). If the user of a Helm chart tries to pass dynamic values to the chart that violate the JSON Schema, Helm reports an error. @@ -602,7 +602,7 @@ Helm chart templates are based on language that can execute arbitrary program logic. Therefore, complex validation can be expressed through conditional logic in the YAML template itself. If validation fails, your template can call the -[fail](/chart_template_guide/function_list#fail) function, which tells Helm to +[fail](/chart_template_guide/function_list.mdx#fail) function, which tells Helm to abort processing the chart with an error. For instance, the following YAML template snippet can be used to set a virtual From 7cb9e22567a12bd30005a2add9c61f9c32f331e9 Mon Sep 17 00:00:00 2001 From: Michael Riedel Date: Fri, 3 Jul 2026 21:49:30 +0200 Subject: [PATCH 11/14] Adjust formatting. Signed-off-by: Michael Riedel --- docs/chart_template_guide/yaml_techniques.md | 21 ++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/docs/chart_template_guide/yaml_techniques.md b/docs/chart_template_guide/yaml_techniques.md index eba26e4a9..05214ebb5 100644 --- a/docs/chart_template_guide/yaml_techniques.md +++ b/docs/chart_template_guide/yaml_techniques.md @@ -545,10 +545,10 @@ into your cluster. For example, attackers could: * Create new Service Accounts, (Cluster)Roles, and (Cluster)RoleBindings to escalate their privileges. In order to run a YAML injection attack, an attacker would first need to pass -their own [values](/chart_template_guide/values_files.mdx) to your Helm chart. This -seems unlikely, and in fact it may never happen when you're using your own Helm -charts. Even when consuming Helm charts from other authors, Helm users will -often have full control of the values that they use. +their own [values](/chart_template_guide/values_files.mdx) to your Helm chart. +This seems unlikely, and in fact it may never happen when you're using your own +Helm charts. Even when consuming Helm charts from other authors, Helm users +will often have full control of the values that they use. However, in some *Infrastructure-as-Code* scenarios, users will not pass values to a Helm chart manually through CLI arguments or value files. Instead, users @@ -580,10 +580,11 @@ dynamic values, *Schema Files* and *Validation Logic in Templates*. #### Schema Files -Helm's [Schema Files](/topics/charts.mdx#schema-files) allow chart authors to -validate values against a [JSON Schema](https://json-schema.org/) -(`values.schema.json`). If the user of a Helm chart tries to pass dynamic values -to the chart that violate the JSON Schema, Helm reports an error. +Helm's [Schema Files](/topics/charts.mdx#schema-files) (`values.schema.json`) +allow chart authors to validate values against a +[JSON Schema](https://json-schema.org/). If the user of a Helm chart tries to +pass dynamic values to the chart that violate the JSON Schema, Helm reports an +error. This validation approach is input-centric, as the JSON Schema constrains all values as passed to the Helm chart. This is useful for values that appear @@ -602,8 +603,8 @@ Helm chart templates are based on language that can execute arbitrary program logic. Therefore, complex validation can be expressed through conditional logic in the YAML template itself. If validation fails, your template can call the -[fail](/chart_template_guide/function_list.mdx#fail) function, which tells Helm to -abort processing the chart with an error. +[`fail`](/chart_template_guide/function_list.mdx#fail) function, which tells +Helm to abort processing the chart with an error. For instance, the following YAML template snippet can be used to set a virtual server's domain name only if the given value matches a DNS domain: From 50d931ed3f6c3b87a1a015f3f8bbb09b4dc7642d Mon Sep 17 00:00:00 2001 From: Paige Calvert Date: Tue, 30 Jun 2026 12:55:26 -0600 Subject: [PATCH 12/14] Adds default_lang_commit front matter Signed-off-by: Paige Calvert Signed-off-by: Michael Riedel --- .../version-3/chart_best_practices/conventions.md | 1 + .../chart_best_practices/custom_resource_definitions.md | 1 + .../version-3/chart_best_practices/dependencies.md | 1 + .../version-3/chart_best_practices/labels.md | 1 + .../version-3/chart_best_practices/pods.md | 1 + .../version-3/chart_best_practices/rbac.md | 1 + .../version-3/chart_best_practices/templates.md | 1 + .../version-3/chart_best_practices/values.md | 1 + .../version-3/chart_template_guide/builtin_objects.md | 1 + .../version-3/chart_template_guide/control_structures.md | 1 + .../version-3/chart_template_guide/data_types.md | 1 + .../version-3/chart_template_guide/debugging.md | 1 + .../version-3/chart_template_guide/functions_and_pipelines.md | 1 + .../version-3/chart_template_guide/getting_started.md | 1 + .../version-3/chart_template_guide/notes_files.md | 1 + .../version-3/chart_template_guide/subcharts_and_globals.md | 1 + .../version-3/chart_template_guide/values_files.md | 1 + .../version-3/chart_template_guide/variables.md | 1 + .../version-3/chart_template_guide/wrapping_up.md | 1 + .../version-3/faq/changes_since_helm2.md | 1 + .../docusaurus-plugin-content-docs/version-3/faq/installing.md | 1 + .../docusaurus-plugin-content-docs/version-3/faq/uninstalling.md | 1 + i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm.md | 1 + .../version-3/helm/helm_dependency.md | 1 + .../version-3/helm/helm_dependency_build.md | 1 + .../version-3/helm/helm_dependency_list.md | 1 + .../version-3/helm/helm_dependency_update.md | 1 + .../de/docusaurus-plugin-content-docs/version-3/helm/helm_env.md | 1 + .../de/docusaurus-plugin-content-docs/version-3/helm/helm_get.md | 1 + .../version-3/helm/helm_get_all.md | 1 + .../version-3/helm/helm_get_hooks.md | 1 + .../version-3/helm/helm_get_manifest.md | 1 + .../version-3/helm/helm_get_notes.md | 1 + .../version-3/helm/helm_get_values.md | 1 + .../version-3/helm/helm_history.md | 1 + .../version-3/helm/helm_install.md | 1 + .../docusaurus-plugin-content-docs/version-3/helm/helm_lint.md | 1 + .../docusaurus-plugin-content-docs/version-3/helm/helm_list.md | 1 + .../docusaurus-plugin-content-docs/version-3/helm/helm_plugin.md | 1 + .../version-3/helm/helm_plugin_install.md | 1 + .../version-3/helm/helm_plugin_list.md | 1 + .../version-3/helm/helm_plugin_uninstall.md | 1 + .../version-3/helm/helm_plugin_update.md | 1 + .../docusaurus-plugin-content-docs/version-3/helm/helm_pull.md | 1 + .../docusaurus-plugin-content-docs/version-3/helm/helm_push.md | 1 + .../version-3/helm/helm_registry.md | 1 + .../version-3/helm/helm_registry_login.md | 1 + .../version-3/helm/helm_registry_logout.md | 1 + .../docusaurus-plugin-content-docs/version-3/helm/helm_repo.md | 1 + .../version-3/helm/helm_repo_add.md | 1 + .../version-3/helm/helm_repo_index.md | 1 + .../version-3/helm/helm_repo_list.md | 1 + .../version-3/helm/helm_repo_remove.md | 1 + .../version-3/helm/helm_repo_update.md | 1 + .../version-3/helm/helm_rollback.md | 1 + .../docusaurus-plugin-content-docs/version-3/helm/helm_search.md | 1 + .../version-3/helm/helm_search_hub.md | 1 + .../version-3/helm/helm_search_repo.md | 1 + .../docusaurus-plugin-content-docs/version-3/helm/helm_show.md | 1 + .../version-3/helm/helm_show_all.md | 1 + .../version-3/helm/helm_show_chart.md | 1 + .../version-3/helm/helm_show_crds.md | 1 + .../version-3/helm/helm_show_readme.md | 1 + .../version-3/helm/helm_show_values.md | 1 + .../docusaurus-plugin-content-docs/version-3/helm/helm_status.md | 1 + .../version-3/helm/helm_template.md | 1 + .../docusaurus-plugin-content-docs/version-3/helm/helm_test.md | 1 + .../version-3/helm/helm_uninstall.md | 1 + .../version-3/helm/helm_upgrade.md | 1 + .../docusaurus-plugin-content-docs/version-3/helm/helm_verify.md | 1 + .../version-3/helm/helm_version.md | 1 + .../version-3/howto/chart_repository_sync_example.md | 1 + i18n/de/docusaurus-plugin-content-docs/version-3/howto/index.mdx | 1 + i18n/de/docusaurus-plugin-content-docs/version-3/intro/index.mdx | 1 + .../docusaurus-plugin-content-docs/version-3/intro/using_helm.md | 1 + i18n/de/docusaurus-plugin-content-docs/version-3/sdk/gosdk.md | 1 + .../docusaurus-plugin-content-docs/version-3/topics/advanced.md | 1 + .../version-3/topics/architecture.md | 1 + .../version-3/topics/chart_repository.md | 1 + .../version-3/topics/chart_tests.md | 1 + .../version-3/topics/kubernetes_distros.md | 1 + .../version-3/topics/permissions_sql_storage_backend.md | 1 + .../version-3/topics/provenance.md | 1 + i18n/de/docusaurus-plugin-content-docs/version-3/topics/rbac.md | 1 + .../version-3/topics/registries.md | 1 + .../version-3/topics/v2_v3_migration.md | 1 + .../version-3/topics/version_skew.md | 1 + 87 files changed, 87 insertions(+) diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/conventions.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/conventions.md index 6872efc05..905887e67 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/conventions.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/conventions.md @@ -2,6 +2,7 @@ title: Allgemeine Konventionen description: Allgemeine Konventionen für Charts. sidebar_position: 1 +default_lang_commit: cd6112565cf10522d4f1bd0928165cb5a91922c5 --- Dieser Teil des Best-Practices-Leitfadens erklärt allgemeine Konventionen. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/custom_resource_definitions.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/custom_resource_definitions.md index 89897f78c..c1534df3f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/custom_resource_definitions.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/custom_resource_definitions.md @@ -2,6 +2,7 @@ title: Custom Resource Definitions description: Erstellen und Verwenden von CRDs. sidebar_position: 7 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Dieser Teil des Best-Practices-Leitfadens behandelt die Erstellung und Verwendung von Custom-Resource-Definition-Objekten. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/dependencies.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/dependencies.md index ed9a11d4d..0fa06e8cd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/dependencies.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/dependencies.md @@ -2,6 +2,7 @@ title: Abhängigkeiten description: Behandelt Best Practices für Chart-Abhängigkeiten. sidebar_position: 4 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Dieser Teil des Best-Practices-Leitfadens behandelt die in `Chart.yaml` deklarierten `dependencies`. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/labels.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/labels.md index 7b13efe56..fb8a655c4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/labels.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/labels.md @@ -2,6 +2,7 @@ title: Labels und Annotationen description: Behandelt Best Practices für die Verwendung von Labels und Annotationen in Ihrem Chart. sidebar_position: 5 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Dieser Teil des Best-Practices-Leitfadens behandelt Best Practices für die Verwendung von Labels und Annotationen in Ihrem Chart. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/pods.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/pods.md index ffc0b6d7e..aa994cc21 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/pods.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/pods.md @@ -2,6 +2,7 @@ title: Pods und PodTemplates description: Behandelt die Formatierung von Pod- und PodTemplate-Bereichen in Chart-Manifesten. sidebar_position: 6 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Dieser Teil des Best-Practices-Leitfadens behandelt die Formatierung von Pod- und PodTemplate-Bereichen in Chart-Manifesten. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/rbac.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/rbac.md index 480d8be33..bfc42adff 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/rbac.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/rbac.md @@ -2,6 +2,7 @@ title: Rollenbasierte Zugriffskontrolle description: Behandelt die Erstellung und Formatierung von RBAC-Ressourcen in Chart-Manifesten. sidebar_position: 8 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Dieser Teil des Best-Practices-Leitfadens behandelt die Erstellung und Formatierung von diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/templates.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/templates.md index e2d7e29a2..2ce710ade 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/templates.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/templates.md @@ -2,6 +2,7 @@ title: Templates description: Ein genauerer Blick auf Best Practices rund um Templates. sidebar_position: 3 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Dieser Teil des Best-Practices-Leitfadens konzentriert sich auf Templates. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/values.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/values.md index f40387dff..d7e5a04e2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/values.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_best_practices/values.md @@ -2,6 +2,7 @@ title: Values description: Beschreibt, wie Sie Ihre Values strukturieren und verwenden sollten. sidebar_position: 2 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Dieser Teil des Best-Practices-Leitfadens behandelt die Verwendung von Values. Hier geben wir Empfehlungen, wie Sie Ihre Values strukturieren und verwenden sollten, mit Fokus auf die Gestaltung der `values.yaml`-Datei eines Charts. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/builtin_objects.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/builtin_objects.md index c1c2661d1..9aca0b046 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/builtin_objects.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/builtin_objects.md @@ -2,6 +2,7 @@ title: Integrierte Objekte description: Integrierte Objekte, die in Templates verfügbar sind. sidebar_position: 3 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Objekte werden von der Template-Engine an ein Template übergeben. Ihr Code kann diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/control_structures.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/control_structures.md index 016831a95..8c1a8f71f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/control_structures.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/control_structures.md @@ -2,6 +2,7 @@ title: Ablaufsteuerung description: Ein kurzer Überblick über die Ablaufstrukturen in Templates. sidebar_position: 7 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Kontrollstrukturen (in der Template-Terminologie "Aktionen" genannt) bieten diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/data_types.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/data_types.md index 0e9ae5b17..2b887f7d0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/data_types.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/data_types.md @@ -2,6 +2,7 @@ title: "Anhang: Go-Datentypen und Templates" description: Ein kurzer Überblick über Variablen in Templates. sidebar_position: 16 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Die Helm-Template-Sprache ist in der stark typisierten Programmiersprache Go diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/debugging.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/debugging.md index effa2bd98..8a55ffbdb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/debugging.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/debugging.md @@ -2,6 +2,7 @@ title: Templates debuggen description: Fehlerbehebung bei Charts, die nicht bereitgestellt werden können. sidebar_position: 13 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Das Debuggen von Templates kann schwierig sein, da die gerenderten Templates an diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/functions_and_pipelines.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/functions_and_pipelines.md index 3fdf05706..bd76a3873 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/functions_and_pipelines.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/functions_and_pipelines.md @@ -2,6 +2,7 @@ title: Template-Funktionen und Pipelines description: Verwendung von Funktionen in Templates. sidebar_position: 5 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Bisher haben wir gesehen, wie man Informationen in ein Template einfügt. Aber diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/getting_started.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/getting_started.md index ae4bcf771..321723eb0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/getting_started.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/getting_started.md @@ -2,6 +2,7 @@ title: Erste Schritte description: Eine Kurzanleitung zu Chart-Templates. sidebar_position: 2 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- In diesem Abschnitt der Anleitung erstellen wir ein Chart und fügen dann ein diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/notes_files.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/notes_files.md index 90926fecc..1b9faaeab 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/notes_files.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/notes_files.md @@ -2,6 +2,7 @@ title: Eine NOTES.txt-Datei erstellen description: Wie Sie Ihren Chart-Benutzern Anweisungen bereitstellen. sidebar_position: 10 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- In diesem Abschnitt betrachten wir das Helm-Werkzeug zur Bereitstellung von diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/subcharts_and_globals.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/subcharts_and_globals.md index 909e55f15..685aedbec 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/subcharts_and_globals.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/subcharts_and_globals.md @@ -2,6 +2,7 @@ title: Subcharts und globale Werte description: Arbeiten mit Subchart-Werten und globalen Werten. sidebar_position: 11 +default_lang_commit: 6bf4b4cb62bb3952a17b68b3cd8b832bcede390c --- Bis zu diesem Punkt haben wir nur mit einem einzelnen Chart gearbeitet. Aber diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/values_files.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/values_files.md index d226f39bb..a3e9a9ef9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/values_files.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/values_files.md @@ -2,6 +2,7 @@ title: Values-Dateien description: Anleitung zur Verwendung des --values-Flags. sidebar_position: 4 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Im vorherigen Abschnitt haben wir die eingebauten Objekte betrachtet, die Helm diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/variables.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/variables.md index b2417675e..4f51a7300 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/variables.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/variables.md @@ -2,6 +2,7 @@ title: Variablen description: Verwendung von Variablen in Templates. sidebar_position: 8 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Nachdem wir nun mit Funktionen, Pipelines, Objekten und Kontrollstrukturen diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/wrapping_up.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/wrapping_up.md index 223a6521d..59a6570e2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/wrapping_up.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/wrapping_up.md @@ -2,6 +2,7 @@ title: Nächste Schritte description: Abschluss - einige nützliche Hinweise auf weitere Dokumentation, die Ihnen helfen wird. sidebar_position: 14 +default_lang_commit: 6bf4b4cb62bb3952a17b68b3cd8b832bcede390c --- Diese Anleitung soll Ihnen als Chart-Entwickler ein fundiertes Verständnis diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/faq/changes_since_helm2.md b/i18n/de/docusaurus-plugin-content-docs/version-3/faq/changes_since_helm2.md index df72400ee..7993a6a3c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/faq/changes_since_helm2.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/faq/changes_since_helm2.md @@ -1,6 +1,7 @@ --- title: "Änderungen seit Helm 2" sidebar_position: 1 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- ## Änderungen seit Helm 2 diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/faq/installing.md b/i18n/de/docusaurus-plugin-content-docs/version-3/faq/installing.md index 2f818aaa2..c828c601e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/faq/installing.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/faq/installing.md @@ -1,6 +1,7 @@ --- title: "Installieren" sidebar_position: 2 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- ## Installieren diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/faq/uninstalling.md b/i18n/de/docusaurus-plugin-content-docs/version-3/faq/uninstalling.md index 751bff14c..580f1a0a7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/faq/uninstalling.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/faq/uninstalling.md @@ -1,6 +1,7 @@ --- title: "Deinstallieren" sidebar_position: 3 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- ## Deinstallieren diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm.md index e1feebf32..a20485118 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm.md @@ -1,6 +1,7 @@ --- title: helm slug: helm +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Der Helm-Paketmanager für Kubernetes. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency.md index 33637778d..51e98d5fc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency.md @@ -1,5 +1,6 @@ --- title: helm dependency +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Verwaltet die Abhängigkeiten eines Charts diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_build.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_build.md index 7c6448738..27fe40e70 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_build.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_build.md @@ -1,5 +1,6 @@ --- title: helm dependency build +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Erstellt das Verzeichnis charts/ basierend auf der Chart.lock-Datei neu diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_list.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_list.md index f0db1a3ea..56029c3df 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_list.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_list.md @@ -1,5 +1,6 @@ --- title: helm dependency list +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Listet die Abhängigkeiten für das angegebene Chart auf diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_update.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_update.md index bbc95047b..6ab8582b8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_update.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_dependency_update.md @@ -1,5 +1,6 @@ --- title: helm dependency update +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Aktualisiert charts/ entsprechend dem Inhalt von Chart.yaml diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_env.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_env.md index 59a52ebcd..6f46f9dee 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_env.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_env.md @@ -1,5 +1,6 @@ --- title: helm env +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Informationen zur Helm-Client-Umgebung diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get.md index 65b9c28b6..a3e089ecb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get.md @@ -1,5 +1,6 @@ --- title: helm get +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Lädt erweiterte Informationen für ein benanntes Release herunter diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_all.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_all.md index 4fb8817b4..74991cd7b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_all.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_all.md @@ -1,5 +1,6 @@ --- title: helm get all +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Lädt alle Informationen für ein benanntes Release herunter diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_hooks.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_hooks.md index 55390296c..94b0e71c9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_hooks.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_hooks.md @@ -1,5 +1,6 @@ --- title: helm get hooks +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Lädt alle Hooks für ein benanntes Release herunter diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_manifest.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_manifest.md index 860c2ca25..122735138 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_manifest.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_manifest.md @@ -1,5 +1,6 @@ --- title: helm get manifest +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Lädt das Manifest für ein benanntes Release herunter diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_notes.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_notes.md index d3744a2a6..759309ffd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_notes.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_notes.md @@ -1,5 +1,6 @@ --- title: helm get notes +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Lädt die Notizen für ein benanntes Release herunter diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_values.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_values.md index 58a552dbd..91b39afdb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_values.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_values.md @@ -1,5 +1,6 @@ --- title: helm get values +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Lädt die Values-Datei für ein benanntes Release herunter diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_history.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_history.md index e1f20329e..767dc14e5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_history.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_history.md @@ -1,5 +1,6 @@ --- title: helm history +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Zeigt die Release-Historie an diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_install.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_install.md index 0a2ee63d0..58dd5b401 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_install.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_install.md @@ -1,5 +1,6 @@ --- title: helm install +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Installiert ein Chart diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_lint.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_lint.md index 71f60e1ed..3c5acd5db 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_lint.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_lint.md @@ -1,5 +1,6 @@ --- title: helm lint +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Untersucht ein Chart auf mögliche Probleme diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_list.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_list.md index 25f5ffd26..d8fbbb388 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_list.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_list.md @@ -1,5 +1,6 @@ --- title: helm list +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Listet Releases auf diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin.md index 5da2c2849..e98cde7c5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin.md @@ -1,5 +1,6 @@ --- title: helm plugin +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Helm Plugins installieren, auflisten oder deinstallieren diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_install.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_install.md index f627fbb07..e96b8329f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_install.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_install.md @@ -1,5 +1,6 @@ --- title: helm plugin install +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Installiert ein Helm-Plugin diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_list.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_list.md index e5870401f..67686ef29 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_list.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_list.md @@ -1,5 +1,6 @@ --- title: helm plugin list +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Listet installierte Helm Plugins auf diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_uninstall.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_uninstall.md index 216be34a1..edf7e8b95 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_uninstall.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_uninstall.md @@ -1,5 +1,6 @@ --- title: helm plugin uninstall +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Deinstalliert ein oder mehrere Helm Plugins diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_update.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_update.md index 099e6cd36..c95dec3c7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_update.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_plugin_update.md @@ -1,5 +1,6 @@ --- title: helm plugin update +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Aktualisiert ein oder mehrere Helm Plugins diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_pull.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_pull.md index 1ae99bba5..ebd6a0055 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_pull.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_pull.md @@ -1,5 +1,6 @@ --- title: helm pull +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Ein Chart aus einem Repository herunterladen und (optional) lokal entpacken diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_push.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_push.md index 3adfc647c..7b54eb93b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_push.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_push.md @@ -1,5 +1,6 @@ --- title: helm push +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Ein Chart in eine Registry hochladen diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry.md index fdb3a53b3..c91bb9017 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry.md @@ -1,5 +1,6 @@ --- title: helm registry +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Bei einer Registry an- oder abmelden diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry_login.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry_login.md index c9c68b2c5..6b15cc2e1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry_login.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry_login.md @@ -1,5 +1,6 @@ --- title: helm registry login +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Bei einer Registry anmelden diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry_logout.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry_logout.md index 81fd25e30..468fa1b9b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry_logout.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_registry_logout.md @@ -1,5 +1,6 @@ --- title: helm registry logout +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Von einer Registry abmelden diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo.md index 94a1c17e3..4cbe57aa7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo.md @@ -1,5 +1,6 @@ --- title: helm repo +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Chart Repositories hinzufügen, auflisten, entfernen, aktualisieren und indizieren diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_add.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_add.md index 8a41d616a..31d886c74 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_add.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_add.md @@ -1,5 +1,6 @@ --- title: helm repo add +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Fügt ein Chart Repository hinzu diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_index.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_index.md index 62fa3901f..91939b951 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_index.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_index.md @@ -1,5 +1,6 @@ --- title: helm repo index +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Erstellt eine Indexdatei aus einem Verzeichnis mit gepackten Charts diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_list.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_list.md index 7ffaeb976..6dc015d63 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_list.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_list.md @@ -1,5 +1,6 @@ --- title: helm repo list +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Listet Chart Repositories auf diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_remove.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_remove.md index 2cd3414de..19beebbba 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_remove.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_remove.md @@ -1,5 +1,6 @@ --- title: helm repo remove +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Entfernt ein oder mehrere Chart Repositories diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_update.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_update.md index bcab264e0..a3cbaad27 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_update.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_repo_update.md @@ -1,5 +1,6 @@ --- title: helm repo update +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Aktualisiert lokal die Informationen über verfügbare Charts aus den Chart Repositories diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_rollback.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_rollback.md index f7b9ff51d..94a9751f2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_rollback.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_rollback.md @@ -1,5 +1,6 @@ --- title: helm rollback +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Setzt ein Release auf eine vorherige Revision zurück diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search.md index 16d679691..c77ba091f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search.md @@ -1,5 +1,6 @@ --- title: helm search +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Durchsucht Charts nach einem Suchbegriff diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search_hub.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search_hub.md index 1d1d7f184..78f60adb4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search_hub.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search_hub.md @@ -1,5 +1,6 @@ --- title: helm search hub +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Durchsucht den Artifact Hub oder Ihre eigene Hub-Instanz nach Charts diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search_repo.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search_repo.md index 6f5e17aaf..7d185c3d1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search_repo.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_search_repo.md @@ -1,5 +1,6 @@ --- title: helm search repo +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Durchsucht Repositories nach Charts anhand eines Suchbegriffs diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show.md index 8fd499943..a83425e1e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show.md @@ -1,5 +1,6 @@ --- title: helm show +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Zeigt Informationen zu einem Chart an diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_all.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_all.md index d58bbad7b..98eb3135b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_all.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_all.md @@ -1,5 +1,6 @@ --- title: helm show all +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Zeigt alle Informationen eines Charts an diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_chart.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_chart.md index 773a6b0bb..1228d6983 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_chart.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_chart.md @@ -1,5 +1,6 @@ --- title: helm show chart +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Zeigt die Definition des Charts an diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_crds.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_crds.md index 7c5b9a019..411f3aea2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_crds.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_crds.md @@ -1,5 +1,6 @@ --- title: helm show crds +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Zeigt die CRDs des Charts an diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_readme.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_readme.md index 595033440..324e094cd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_readme.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_readme.md @@ -1,5 +1,6 @@ --- title: helm show readme +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Zeigt die README-Datei des Charts an diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_values.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_values.md index 8f0d84c33..9705d4c45 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_values.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_show_values.md @@ -1,5 +1,6 @@ --- title: helm show values +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Zeigt die Werte des Charts an diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_status.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_status.md index 07628296d..15b75a7c2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_status.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_status.md @@ -1,5 +1,6 @@ --- title: helm status +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Zeigt den Status eines benannten Releases an diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_template.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_template.md index 6d5379a92..678c61347 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_template.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_template.md @@ -1,5 +1,6 @@ --- title: helm template +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Rendert Templates lokal diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_test.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_test.md index 2b82a9da2..50ec65b9a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_test.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_test.md @@ -1,5 +1,6 @@ --- title: helm test +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Führt Tests für ein Release aus diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_uninstall.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_uninstall.md index 7e87e7646..fec42eabe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_uninstall.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_uninstall.md @@ -1,5 +1,6 @@ --- title: helm uninstall +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Deinstalliert ein Release diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_upgrade.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_upgrade.md index c4ee64598..6ca6d4ebb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_upgrade.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_upgrade.md @@ -1,5 +1,6 @@ --- title: helm upgrade +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Aktualisiert ein Release auf eine neue Version eines Charts diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_verify.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_verify.md index 159fcbd95..42a067f2f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_verify.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_verify.md @@ -1,5 +1,6 @@ --- title: helm verify +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Überprüft, ob ein Chart am angegebenen Pfad signiert wurde und gültig ist diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_version.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_version.md index 9ce5d887f..b77ec783f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_version.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_version.md @@ -1,5 +1,6 @@ --- title: helm version +default_lang_commit: 5882b9b38eba10f3ecb6da25566f9809baf797f0 --- Gibt die Client-Versionsinformationen aus diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/howto/chart_repository_sync_example.md b/i18n/de/docusaurus-plugin-content-docs/version-3/howto/chart_repository_sync_example.md index 7212e9133..033a1b5a6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/howto/chart_repository_sync_example.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/howto/chart_repository_sync_example.md @@ -2,6 +2,7 @@ title: "Synchronisieren Ihres Chart Repository" description: "Beschreibt wie Sie lokale und entfernte Chart Repositories synchronisieren." sidebar_position: 2 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- *Hinweis: Dieses Beispiel richtet sich an einen Google Cloud Storage (GCS) Bucket, diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/howto/index.mdx b/i18n/de/docusaurus-plugin-content-docs/version-3/howto/index.mdx index c8e80a63d..82c0bac20 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/howto/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/howto/index.mdx @@ -1,6 +1,7 @@ --- title: "Lernprogramme" sidebar_position: 2 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- # Wie-geht-Anleitungen (How-Tos) diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/intro/index.mdx b/i18n/de/docusaurus-plugin-content-docs/version-3/intro/index.mdx index 348c3b6d5..590b30bcb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/intro/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/intro/index.mdx @@ -1,6 +1,7 @@ --- title: "Einführung" sidebar_position: 1 +default_lang_commit: 32156809d1ef7c7445cabb92c46ffcea328ac6be --- # Einführung in Helm diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/intro/using_helm.md b/i18n/de/docusaurus-plugin-content-docs/version-3/intro/using_helm.md index cebc26fff..9b64ad420 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/intro/using_helm.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/intro/using_helm.md @@ -2,6 +2,7 @@ title: "Helm benutzen" description: "Erklärt die Grundsätze zu Helm." sidebar_position: 3 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Diese Anleitung erklärt die Grundlagen zur Benutzung von Helm, um Pakete in Ihrem Kubernetes diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/sdk/gosdk.md b/i18n/de/docusaurus-plugin-content-docs/version-3/sdk/gosdk.md index fc6a4f93d..3a21810b8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/sdk/gosdk.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/sdk/gosdk.md @@ -2,6 +2,7 @@ title: Einführung description: Stellt das Helm Go SDK vor sidebar_position: 1 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Das Go SDK von Helm ermöglicht es benutzerdefinierter Software, Helm Charts und die Funktionalität von Helm für die Verwaltung von Kubernetes-Software-Deployments zu nutzen. (Die Helm CLI ist im Grunde selbst nur ein solches Werkzeug!) diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/advanced.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/advanced.md index 69e87b305..267d3ea7a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/advanced.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/advanced.md @@ -2,6 +2,7 @@ title: Fortgeschrittene Helm-Techniken description: Erläutert verschiedene fortgeschrittene Funktionen für erfahrene Helm-Benutzer sidebar_position: 9 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Dieser Abschnitt erläutert verschiedene fortgeschrittene Funktionen und Techniken für die Verwendung von Helm. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/architecture.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/architecture.md index 55f46814c..94fb07db4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/architecture.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/architecture.md @@ -2,6 +2,7 @@ title: Helm Architektur description: Beschreibt die Architektur von Helm auf hoher Ebene. sidebar_position: 8 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- # Helm Architektur diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/chart_repository.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/chart_repository.md index 8d0430203..040cc6f13 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/chart_repository.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/chart_repository.md @@ -2,6 +2,7 @@ title: Leitfaden für Chart Repositories description: So erstellen und arbeiten Sie mit Helm Chart Repositories. sidebar_position: 6 +default_lang_commit: 944aeaca4df514e7c5ba091995fcbbc08e505f65 --- Dieser Abschnitt erklärt, wie Sie Chart Repositories erstellen und damit arbeiten. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/chart_tests.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/chart_tests.md index 720bb0591..5a33ae9fc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/chart_tests.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/chart_tests.md @@ -2,6 +2,7 @@ title: Chart Tests description: Beschreibt, wie Sie Ihre Charts ausführen und testen können. sidebar_position: 3 +default_lang_commit: 81fa9227414a9c99d74705bdc159c4c21c9aac7c --- Ein Chart enthält eine Reihe von Kubernetes-Ressourcen und Komponenten, die zusammenarbeiten. Als Chart-Autor möchten Sie möglicherweise Tests schreiben, die überprüfen, ob Ihr Chart bei der Installation wie erwartet funktioniert. Diese Tests helfen auch dem Chart-Benutzer zu verstehen, was Ihr Chart tun soll. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/kubernetes_distros.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/kubernetes_distros.md index 5808aebc8..9d308c6d0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/kubernetes_distros.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/kubernetes_distros.md @@ -2,6 +2,7 @@ title: Leitfaden für Kubernetes-Distributionen description: Enthält Informationen zur Verwendung von Helm in bestimmten Kubernetes-Umgebungen. sidebar_position: 10 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Helm sollte mit jeder [konformen Version von diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/permissions_sql_storage_backend.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/permissions_sql_storage_backend.md index f61b0996d..55743ff0b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/permissions_sql_storage_backend.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/permissions_sql_storage_backend.md @@ -1,6 +1,7 @@ --- title: Berechtigungsverwaltung für das SQL-Speicher-Backend description: Erfahren Sie, wie Sie Berechtigungen bei Verwendung des SQL-Speicher-Backends einrichten. +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Dieses Dokument bietet eine Anleitung zur Einrichtung und Verwaltung von diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/provenance.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/provenance.md index 991ca9271..b624c5dfe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/provenance.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/provenance.md @@ -2,6 +2,7 @@ title: Helm-Provenienz und -Integrität description: Beschreibt, wie Sie die Integrität und Herkunft eines Charts überprüfen können. sidebar_position: 5 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Helm verfügt über Provenienz-Werkzeuge, die Chart-Benutzern helfen, die Integrität und diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/rbac.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/rbac.md index 318066298..357fb2718 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/rbac.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/rbac.md @@ -2,6 +2,7 @@ title: Rollenbasierte Zugriffskontrolle description: Erläutert, wie Helm mit der rollenbasierten Zugriffskontrolle (RBAC) von Kubernetes interagiert. sidebar_position: 11 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- In Kubernetes ist es eine Best Practice, Benutzern oder anwendungsspezifischen diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/registries.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/registries.md index 1710d38a3..6e22f1379 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/registries.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/registries.md @@ -2,6 +2,7 @@ title: OCI-basierte Registries verwenden description: Beschreibt die Verwendung von OCI für die Chart-Verteilung. sidebar_position: 7 +default_lang_commit: 2e15490c82d246093e11e418a7c23907a4afa89e --- Seit Helm 3 können Sie Container-Registries mit [OCI](https://www.opencontainers.org/)-Unterstützung verwenden, um Chart-Pakete zu speichern und zu teilen. Ab Helm v3.8.0 ist die OCI-Unterstützung standardmäßig aktiviert. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/v2_v3_migration.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/v2_v3_migration.md index 37619793e..370766ae7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/v2_v3_migration.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/v2_v3_migration.md @@ -2,6 +2,7 @@ title: Migration von Helm v2 auf v3 description: Erfahren Sie, wie Sie Helm v2 auf v3 migrieren. sidebar_position: 13 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Diese Anleitung zeigt, wie Sie Helm v2 auf v3 migrieren. Helm v2 muss installiert sein diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/version_skew.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/version_skew.md index 4021d224c..17c2a4851 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/version_skew.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/version_skew.md @@ -1,6 +1,7 @@ --- title: "Helm Versionsunterstützung" description: "Beschreibt die Patch-Release-Richtlinie von Helm sowie die maximal unterstützte Versionsabweichung zwischen Helm und Kubernetes." +default_lang_commit: d9bd24cdc719cd5ddef925552a7049cfbd6f469e --- Dieses Dokument beschreibt die maximal unterstützte Versionsabweichung zwischen Helm und From 35caf26edd742d048f082a5a17d918c286f7f972 Mon Sep 17 00:00:00 2001 From: Paige Calvert Date: Tue, 30 Jun 2026 15:04:21 -0600 Subject: [PATCH 13/14] add default_lang_commit for remaining de version-3 files Signed-off-by: Paige Calvert Signed-off-by: Michael Riedel --- .../version-3/chart_template_guide/accessing_files.md | 1 + .../version-3/chart_template_guide/function_list.md | 1 + .../version-3/chart_template_guide/helm_ignore_file.md | 1 + .../version-3/chart_template_guide/named_templates.md | 1 + .../version-3/chart_template_guide/yaml_techniques.md | 1 + .../de/docusaurus-plugin-content-docs/version-3/faq/index.mdx | 3 ++- .../version-3/faq/troubleshooting.md | 1 + .../version-3/glossary/index.mdx | 3 ++- .../version-3/helm/helm_completion.md | 1 + .../version-3/helm/helm_completion_bash.md | 1 + .../version-3/helm/helm_completion_fish.md | 1 + .../version-3/helm/helm_completion_powershell.md | 1 + .../version-3/helm/helm_completion_zsh.md | 1 + .../version-3/helm/helm_create.md | 1 + .../version-3/helm/helm_get_metadata.md | 1 + .../version-3/helm/helm_package.md | 1 + .../version-3/howto/chart_releaser_action.md | 1 + .../version-3/howto/charts_tips_and_tricks.md | 1 + i18n/de/docusaurus-plugin-content-docs/version-3/index.mdx | 4 +++- .../version-3/intro/CheatSheet.md | 1 + .../docusaurus-plugin-content-docs/version-3/intro/install.md | 1 + .../version-3/intro/quickstart.md | 1 + .../docusaurus-plugin-content-docs/version-3/topics/charts.md | 1 + .../version-3/topics/charts_hooks.md | 1 + .../version-3/topics/kubernetes_apis.md | 1 + .../version-3/topics/library_charts.md | 1 + .../version-3/topics/plugins.md | 1 + 27 files changed, 31 insertions(+), 3 deletions(-) diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/accessing_files.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/accessing_files.md index 7a96f0aa8..7c23d8faf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/accessing_files.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/accessing_files.md @@ -2,6 +2,7 @@ title: Zugriff auf Dateien innerhalb von Templates description: Wie Sie auf Dateien innerhalb eines Templates zugreifen können. sidebar_position: 10 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Im vorherigen Abschnitt haben wir mehrere Möglichkeiten kennengelernt, benannte diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/function_list.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/function_list.md index 56ab32d2a..1568558c2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/function_list.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/function_list.md @@ -2,6 +2,7 @@ title: Liste der Template-Funktionen description: Eine Liste der in Helm verfügbaren Template-Funktionen sidebar_position: 6 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Helm enthält viele Template-Funktionen, die Sie in Templates nutzen können. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/helm_ignore_file.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/helm_ignore_file.md index 8579a0c9b..e308bd46f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/helm_ignore_file.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/helm_ignore_file.md @@ -2,6 +2,7 @@ title: Die .helmignore-Datei description: Die `.helmignore`-Datei wird verwendet, um Dateien anzugeben, die Sie nicht in Ihr Helm Chart aufnehmen möchten. sidebar_position: 12 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Die `.helmignore`-Datei wird verwendet, um Dateien anzugeben, die Sie nicht in diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/named_templates.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/named_templates.md index 4edcfa696..c9df225ab 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/named_templates.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/named_templates.md @@ -2,6 +2,7 @@ title: Benannte Templates description: Wie man benannte Templates definiert. sidebar_position: 9 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Nun ist es an der Zeit, über ein einzelnes Template hinauszugehen und weitere zu diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/yaml_techniques.md b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/yaml_techniques.md index 76ebddb7d..a35ab45bb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/yaml_techniques.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/chart_template_guide/yaml_techniques.md @@ -2,6 +2,7 @@ title: "Anhang: YAML-Techniken" description: Ein genauerer Blick auf die YAML-Spezifikation und wie sie auf Helm angewendet wird. sidebar_position: 15 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Der Großteil dieser Anleitung hat sich auf das Schreiben der Template-Sprache diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/faq/index.mdx b/i18n/de/docusaurus-plugin-content-docs/version-3/faq/index.mdx index 296eaf030..e7c2b74fc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/faq/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/faq/index.mdx @@ -1,6 +1,7 @@ --- title: "Fragen und Antworten" -sidebar_position: 8 +sidebar_position: 9 +default_lang_commit: 32156809d1ef7c7445cabb92c46ffcea328ac6be --- # Fragen und Antworten diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/faq/troubleshooting.md b/i18n/de/docusaurus-plugin-content-docs/version-3/faq/troubleshooting.md index 274ef236f..1f0037b25 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/faq/troubleshooting.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/faq/troubleshooting.md @@ -1,6 +1,7 @@ --- title: "Fehlersuche" sidebar_position: 4 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- ## Fehlersuche diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/glossary/index.mdx b/i18n/de/docusaurus-plugin-content-docs/version-3/glossary/index.mdx index 68cee136c..bdac076a1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/glossary/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/glossary/index.mdx @@ -1,7 +1,8 @@ --- title: "Glossar" description: "Benutzte Ausdrücke zur Beschreibung der Komponenten der Helm Architektur." -sidebar_position: 9 +sidebar_position: 10 +default_lang_commit: 32156809d1ef7c7445cabb92c46ffcea328ac6be --- # Glossar diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion.md index daf93a52c..af7585ce6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion.md @@ -1,5 +1,6 @@ --- title: helm completion +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Generiert Autovervollständigungsskripte für die angegebene Shell diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_bash.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_bash.md index 70e291bbb..97eb1827b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_bash.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_bash.md @@ -1,5 +1,6 @@ --- title: helm completion bash +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Generiert das Autovervollständigungsskript für bash diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_fish.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_fish.md index e50bd5a57..c7d51ee85 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_fish.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_fish.md @@ -1,5 +1,6 @@ --- title: helm completion fish +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Generiert das Autovervollständigungsskript für fish diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_powershell.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_powershell.md index 6f2a16c0b..1b5fbee83 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_powershell.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_powershell.md @@ -1,5 +1,6 @@ --- title: helm completion powershell +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Generiert das Autovervollständigungsskript für PowerShell diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_zsh.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_zsh.md index 5e20423cb..47e3e7863 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_zsh.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_completion_zsh.md @@ -1,5 +1,6 @@ --- title: helm completion zsh +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Generiert das Autovervollständigungsskript für zsh diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_create.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_create.md index 146a61332..0e8dd7c6c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_create.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_create.md @@ -1,5 +1,6 @@ --- title: helm create +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Erstellt ein neues Chart mit dem angegebenen Namen diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_metadata.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_metadata.md index 3390ffc90..aece8c5fa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_metadata.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_get_metadata.md @@ -1,5 +1,6 @@ --- title: helm get metadata +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Ruft die Metadaten für ein bestimmtes Release ab diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_package.md b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_package.md index fe0c1282c..1b9e0a45a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_package.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/helm/helm_package.md @@ -1,5 +1,6 @@ --- title: helm package +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Ein Chart-Verzeichnis in ein Chart-Archiv paketieren diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/howto/chart_releaser_action.md b/i18n/de/docusaurus-plugin-content-docs/version-3/howto/chart_releaser_action.md index a4d7c4517..bc62182bc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/howto/chart_releaser_action.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/howto/chart_releaser_action.md @@ -2,6 +2,7 @@ title: Chart Releaser Action zur Automatisierung von GitHub Pages Charts description: Beschreibt, wie Sie die Chart Releaser Action verwenden, um die Veröffentlichung von Charts über GitHub Pages zu automatisieren. sidebar_position: 3 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Diese Anleitung beschreibt, wie Sie die [Chart Releaser diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/howto/charts_tips_and_tricks.md b/i18n/de/docusaurus-plugin-content-docs/version-3/howto/charts_tips_and_tricks.md index dcb1447b2..adff360f5 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/howto/charts_tips_and_tricks.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/howto/charts_tips_and_tricks.md @@ -2,6 +2,7 @@ title: "Chart Entwicklung Tipps und Tricks" description: "Bespricht Tipps und Tricks,die Helm Chart Entwickler bei der Entwicklung von produktionsreifer Charts gelernt haben." sidebar_position: 1 +default_lang_commit: dab98b270b8063741fb595e80f706fa0b867a8be --- Dieses Handbuch bespricht Tipps und Tricks, die Helm Chart Entwickler bei der Entwicklung von produktionsreifen Charts gelernt haben. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/index.mdx b/i18n/de/docusaurus-plugin-content-docs/version-3/index.mdx index 2ce4e67c3..59673fba0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/index.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/index.mdx @@ -1,6 +1,8 @@ --- title: "Dokumentation" description: "Alles Wissenswerte zur Organisation der Dokumentation." +sidebar_position: 1 +default_lang_commit: 9f8c5e5d797d2c708ffc948c00f56aead761013a --- # Willkommen @@ -14,7 +16,7 @@ Manager für Kubernetes. Genauere Hintergrundinformationen gibt es im Helm hat eine Menge Dokumentation. Eine Hauptübersicht ist hilfreich, nach bestimmten Dingen zu suchen: -- [Lernprogramme](/intro/index.mdx) sind eine gute Handhabe, um das erste Helm Chart zu +- [Lernprogramme](/chart_template_guide/getting_started.md) sind eine gute Handhabe, um das erste Helm Chart zu erstellen. Starten Sie hier, wenn Sie neu bei Helm sind. - [Themenhandbücher](/topics/index.mdx) diskutieren Hauptthemen und Konzepte auf einem hohen Niveau und stellen nützliche Hintergrundinformationen und Erklärungen diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/intro/CheatSheet.md b/i18n/de/docusaurus-plugin-content-docs/version-3/intro/CheatSheet.md index e1b1abc12..1eac750bd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/intro/CheatSheet.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/intro/CheatSheet.md @@ -2,6 +2,7 @@ title: Spickzettel description: Helm Spickzettel sidebar_position: 4 +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Dieser Helm Spickzettel enthält alle notwendigen Befehle, die Sie zur Verwaltung einer Anwendung mit Helm benötigen. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/intro/install.md b/i18n/de/docusaurus-plugin-content-docs/version-3/intro/install.md index 4e08ca4a1..fe30a71ab 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/intro/install.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/intro/install.md @@ -2,6 +2,7 @@ title: "Helm installieren" description: "Lernen Sie wie man Helm installiert und zum Laufen kriegt." sidebar_position: 2 +default_lang_commit: 042b2178fb9384a9d4fe774f210d6db402f3da02 --- Diese Anleitung zeigt, wie Helm CLI zu installieren ist. Helm kann sowohl diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/intro/quickstart.md b/i18n/de/docusaurus-plugin-content-docs/version-3/intro/quickstart.md index ef7a12824..8c896bd0f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/intro/quickstart.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/intro/quickstart.md @@ -2,6 +2,7 @@ title: "Schnellstartanleitung" description: "Wie mit Helm anfangen, incl. Anleitungen für Distributionen, FAQs und Plugins." sidebar_position: 1 +default_lang_commit: e5a8a262fa2a2852a8f3dc0c83260363fff4dced --- Mit dieser Anleitung können Sie schnell mit Helm starten. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/charts.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/charts.md index d6d323ee2..1321f2aa6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/charts.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/charts.md @@ -2,6 +2,7 @@ title: Charts description: Erklärt das Chart-Format und bietet grundlegende Anleitungen zum Erstellen von Charts mit Helm. sidebar_position: 1 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Helm verwendet ein Paketformat namens _Charts_. Ein Chart ist eine Sammlung von Dateien, die zusammengehörige Kubernetes-Ressourcen beschreiben. Mit einem einzelnen Chart lässt sich etwas Einfaches wie ein Memcached-Pod bereitstellen, aber auch etwas Komplexes wie ein vollständiger Web-App-Stack mit HTTP-Servern, Datenbanken, Caches usw. diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/charts_hooks.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/charts_hooks.md index 37cc89091..4726c62fe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/charts_hooks.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/charts_hooks.md @@ -2,6 +2,7 @@ title: Chart Hooks description: Beschreibt die Arbeit mit Chart Hooks. sidebar_position: 2 +default_lang_commit: 6bf4b4cb62bb3952a17b68b3cd8b832bcede390c --- Helm bietet einen _Hook_-Mechanismus, der es Chart-Entwicklern ermöglicht, an diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/kubernetes_apis.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/kubernetes_apis.md index b067f2ab7..3811462d0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/kubernetes_apis.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/kubernetes_apis.md @@ -1,6 +1,7 @@ --- title: Veraltete Kubernetes-APIs description: Erläutert veraltete Kubernetes-APIs im Kontext von Helm +default_lang_commit: 07caa4dd6e58a47e79ac2ec7949e57157f1a2b2a --- Kubernetes ist ein API-gesteuertes System. Die API entwickelt sich im Laufe der diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/library_charts.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/library_charts.md index ad7d6accd..851067fb4 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/library_charts.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/library_charts.md @@ -2,6 +2,7 @@ title: Library Charts description: Erläutert Library Charts und zeigt Anwendungsbeispiele sidebar_position: 4 +default_lang_commit: f1c342d7bbd8fca5494262a93699b27012859e24 --- Ein Library Chart ist ein spezieller Typ von [Helm Chart](/topics/charts.md), diff --git a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/plugins.md b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/plugins.md index d44610f7f..476e9c440 100644 --- a/i18n/de/docusaurus-plugin-content-docs/version-3/topics/plugins.md +++ b/i18n/de/docusaurus-plugin-content-docs/version-3/topics/plugins.md @@ -2,6 +2,7 @@ title: Der Helm Plugins Leitfaden description: Erklärt, wie Sie Plugins verwenden und erstellen können, um die Funktionalität von Helm zu erweitern. sidebar_position: 12 +default_lang_commit: 9f8c5e5d797d2c708ffc948c00f56aead761013a --- Ein Helm Plugin ist ein Werkzeug, das über die `helm` CLI aufgerufen werden kann, From dc6ade44b48d3f96d3e428d306a286ec18186ac6 Mon Sep 17 00:00:00 2001 From: Paige Calvert Date: Tue, 30 Jun 2026 15:15:20 -0600 Subject: [PATCH 14/14] add default_lang_commit for community release policy page Signed-off-by: Paige Calvert Signed-off-by: Michael Riedel --- .../current/release_policy.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/i18n/de/docusaurus-plugin-content-docs-community/current/release_policy.md b/i18n/de/docusaurus-plugin-content-docs-community/current/release_policy.md index 250e9e0fd..95e3019a2 100644 --- a/i18n/de/docusaurus-plugin-content-docs-community/current/release_policy.md +++ b/i18n/de/docusaurus-plugin-content-docs-community/current/release_policy.md @@ -1,6 +1,7 @@ --- title: "Release-Zeitplan-Richtlinie" description: "Beschreibt Helms Release-Zeitplan-Richtlinie." +default_lang_commit: cd5ad1e1593c50677909d7c618cf31cd4036fac7 --- Helm gibt Veröffentlichungstermine im Voraus bekannt, damit Anwender besser planen @@ -27,10 +28,11 @@ einmal im Monat am zweiten Mittwoch jedes Monats veröffentlicht. Ein Patch-Release zur Behebung einer kritischen Regression oder eines Sicherheitsproblems kann jederzeit bei Bedarf erfolgen. -Ein Patch-Release wird aus einem der folgenden Gründe abgesagt: +Ein geplanter Patch-Release wird aus einem der folgenden Gründe abgesagt: - wenn seit dem letzten Release kein neuer Inhalt hinzugekommen ist - wenn das Patch-Release-Datum innerhalb einer Woche vor dem ersten Release Candidate (RC1) einer anstehenden Nebenversion liegt - wenn das Patch-Release-Datum innerhalb von vier Wochen nach einer Nebenversion liegt +- wenn für denselben Monat ein Major- oder Minor-Release geplant ist ## Nebenversionen