Feature Request: a way to only deploy to targets in the fleet yaml

[dbones]

Is your feature request related to a problem?

no

Solution you'd like

in the gitRepo it has a targets which represents all possible servers a git repository is allowed to deploy to

it would be helpful, in the fleet.yaml to be able to specify only the targets it requires to deploy to (and no other target will be deployed to)

this will allow for promotion/targeting to chosen clusters only

Alternatives you've considered

this works, as the other clusters have "nothing" deployed to them, however its not obvious, goes against current fleet, and the dashboards in the Rancher UI shjows a lot of things being deployed which have nothing actually being deployed (its very counter-intuitive)

# defuault is to deploy nothing
helm:
  chart: empty
  repo: https://dbones-labs.github.io/maps
  version: 1.0.0

targetCustomizations:
- name: dev
  clusterSelector:
    matchLabels:
      mycloud/env: dev
  helm:
    chart: kuma
    repo: https://kumahq.github.io/charts
    version: 2.9.3

- name: qa
  clusterSelector:
    matchLabels:
      mycloud/env: qa
  helm:
    chart: kuma
    repo: https://kumahq.github.io/charts
    version: 2.9.3

Anything else?

No response

[matletix]

overrideTargets section in the fleet.yaml file seems to do what you want. From https://fleet.rancher.io/ref-fleet-yaml :

# Override targets defined in the GitRepo. The Bundle will not have any targets
# from the GitRepo if overrideTargets is provided.
overrideTargets:
  - clusterSelector:
      matchLabels:
        env: dev

[dbones]

overrideTargets section in the fleet.yaml file seems to do what you want. From https://fleet.rancher.io/ref-fleet-yaml :

# Override targets defined in the GitRepo. The Bundle will not have any targets
# from the GitRepo if overrideTargets is provided.
overrideTargets:
  - clusterSelector:
      matchLabels:
        env: dev

The overrideTargets looks to ignore the gitRepo. "the bundle will not inherit targets from the GitRepo."

This is is not the intent I am after. I want the gitRepo to provide the super set of available clusters to that repo (constraining the total targets the repo is allowed to deploy to)

in the fleet yaml, this can only target clusters set in the gitRepo. And to provide a way to deploy through environments, without default to deploy to all of the clusters

I hope this makes sense, along with the initial destination above