Document behavior of non-existing clusterLabels
if they are used as value reference.
This commit is contained in:
parent
1e43bcb076
commit
7776827c41
|
|
@ -90,6 +90,8 @@ helm:
|
|||
any-custom: value
|
||||
# All labels on Rancher clusters are available using global.fleet.clusterLabels.LABELNAME
|
||||
# These can now be accessed directly as variables
|
||||
# The variable's value will be an empty string if the referenced cluster label does not
|
||||
# exist on the targeted cluster
|
||||
variableName: global.fleet.clusterLabels.LABELNAME
|
||||
# Path to any values files that need to be passed to helm during install
|
||||
valuesFiles:
|
||||
|
|
|
|||
Loading…
Reference in New Issue