When looking at the gitrepo it would appear as though the targetCustomization isn't working properly. The web UI view suggests there are resources created for the wrong environments via the clusterSelector. I've checked the master cluster for these additional resources that shouldn't be there and I can confirm they weren't created. I can also confirm that from a helm perspective all seems to be working properly. When retrieving the values file from the helm bundle i get back only the values meant for the TEST environment. If i was using the below in fleet.yaml then looking at rancher web UI would suggest that all 3 values sections were merged/used at once when only TEST used be used. My clusters name is called local. It has a label "env=test".

targetCustomizations:
- name: dev
  helm:
    values:
      replication: false
  clusterSelector:
    matchLabels:
      env: dev

- name: test
  helm:
    values:
      replicas: 3
  clusterSelector:
    matchLabels:
      env: test

- name: prod
  helm:
    values:
      serviceType: LoadBalancer
      replicas: 3
  clusterSelector:
    matchLabels:
      env: prod