Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
dbones opened this issue Jan 25, 2025 · 0 comments
Open

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

dbones opened this issue Jan 25, 2025 · 0 comments

Comments

@dbones
Copy link

dbones commented Jan 25, 2025

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)

Image

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant