Feature Request: Allow deployment of a helm chart into multiple namespaces on the same cluster

[cjohn001]

Is your feature request related to a problem?

I think it is a common sceneario that dev, staging and prod deployments coexist in the same cluster in different projects. Currently, if one likes to deploy the same helm chart into multiple namespaces one has to store copies of the helm chart one for each deployment with a custom fleet.yaml. It would already be a solution if relative paths could be made possible, than a gitlab repo structure could be as follows:

• helm chart
• deploy prod
  • fleet.yaml referencing ../helm chart (seems like relative paths currently do not work)
• deploy staging
  • fleet.yaml referencing ../helm chart
• deploy dev
  • fleet.yaml referencing ../helm chart

Solution you'd like

Allowing relative paths to a helm chart would likely work.

Alternatives you've considered

I am new to fleet. Have not found any solution or workaround to the problme so far.

Anything else?

No response

[wangdong-sd]

Any movement for this issue?
Actually I want to have the same feature with kustomize.

[shane-davidson]

Please consider implementing this, I don't think I could upvote it enough. We run 6 different rancher instances (with ~600 clusters and ~20,000 bundle deployments total) but are still considering the effort of moving to argo because of lack of support for this

Just some of the related issues:

#39

#210

#344

#503

#851

#2002

[devsymo]

Seconded on needing this feature. Seem's counter-intuitive not having it

[kkaempf]

#210 was closed and should provide the respective feature.

What else is missing ?

[kkaempf]

Just some of the related issues:

#39

#39 is closed.

#210

#210 is closed.

#344

#344 is closed.

#503

#503 is closed.

#851

#851 is still open.

#2002

#2002 is closed as wontfix.

I'm now closing this issue as well as a duplicate of #210.

If #851 is relevant for you, please comment there.