You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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 toit 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)
Anything else?
No response
The text was updated successfully, but these errors were encountered: