Document behavior of non-existing clusterLabels

if they are used as value reference.
This commit is contained in:
Tim Hardeck 2022-11-21 17:36:39 +01:00
parent 1e43bcb076
commit 7776827c41
No known key found for this signature in database
GPG Key ID: A67C496765D6E0C0
1 changed files with 2 additions and 0 deletions

View File

@ -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: