I am finding a behavior from Fleet very buggy, I deployed I test it deploying this fleet example https://github.com/rancher/fleet-examples/tree/master/single-cluster/helm It deployes well, I was even able to add a label from a value on fleet.yaml or values.yaml Then I tried using variableName: global.fleet.clusterLabels.LABELNAME on fleet.yaml as per documentation and on the helm chart {{ .Values.LABELNAME }} it did not work, even worst, after than the bundle or cluster doesnt update, no matter what I do

Hi @hundreds-terabyte-36933. Here you are an example: https://github.com/juanbrny/fleet-examples/tree/master/single-cluster/helm. It' works as expected. All my clusters have a label called "testid" and I use fleet to inject the value of that cluster label on a helm variable that is used to customize the deployments. Please, have a look and let me know.

Juan, I am trying to demonstrate to my customer the benefits of using GitOps, it is just a proof of concept. Even though I like the Rancher ecosystem and we are still using all other features for the GitOps approach we have decided for now to go with GitOps and Crossplane

@quick-sandwich-76600 - I’m attempting to work through the solution you’ve provided, thank you.