Skip to content

Commit d56d3d7

Browse files
authored
Reorder sentence (#5408)
This order seems easier to understand at least to a non-native-speaker. Signed-off-by: Marcin Owsiany <[email protected]>
1 parent b26427b commit d56d3d7

File tree

1 file changed

+1
-1
lines changed
  • website/content/en/docs/building-operators/helm/reference/advanced_features

1 file changed

+1
-1
lines changed

website/content/en/docs/building-operators/helm/reference/advanced_features/override_values.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ With the helm Operator this becomes possible by override values. This enforces t
1515
template values provided by the chart's default `values.yaml` or by a CR spec are always set
1616
when rendering the chart. If the value is set by a CR it gets overridden by the global override value.
1717
The override value can be static but can also refer to an environment variable and use go templates.
18-
To pass down environment variables to the chart override values is currently the only way.
18+
Using override values is currently the only way to pass down environment variables to the chart.
1919

2020
An example use case of this is when your helm chart references container images by chart variables,
2121
which is a good practice.

0 commit comments

Comments
 (0)