Hi @everyone, I used the following config with doNotDeploy set to true in fleet.yaml so that redis will not be deployed in the matched cluster(cluster1).

namespace: fleet-default

targetCustomizations:
- name: redis
  clusterName: cluster1
  clusterSelector:
    matchLabels:
      env: cluster1
  doNotDeploy: true

ref: https://fleet.rancher.io/ref-fleet-yaml it works as expected as I can't see the deployment in cluster1 from kubeshell or if I navigate to cluster from UI, however the UI in continuous delivery under resources tab shows that it was deployed there and clicking on it dispays the attached error. How can I restrict in UI as this will confuse the user Thread in Slack Conversation