-
Notifications
You must be signed in to change notification settings - Fork 217
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: variables in targetCustomizations? #1395
Comments
If i understand correctly those 2 relate to the helm values? I was hoping for sth like the following, but i can see that that might create more problems. targetCustomizations:
- name: ${ global.fleet.clusterLabels.management.cattle.io/cluster-name }
clusterName: ${ global.fleet.clusterLabels.management.cattle.io/cluster-name }
kustomize:
dir: kustomize/${ global.fleet.clusterLabels.management.cattle.io/cluster-name } Will think about that over the weekend, thank you ;) |
I am also interested in such a solution |
I have
And it turns out that this has become error prone in that devs are adding the overlay dir but forget to add the cluster name into the |
I just found this https://fleet.rancher.io/ref-fleet-yaml#templating on the "Next" docs. That would be really neat and we could hopefully use sth. like this instead of currently 354 lines containing only targetCustomizations ;) : targetCustomizations:
- name: ${ get .ClusterLabels global.fleet.clusterLabels.management.cattle.io/cluster-name }
clusterName: ${ get .ClusterLabels global.fleet.clusterLabels.management.cattle.io/cluster-name }
kustomize:
dir: kustomize/${ get .ClusterLabels global.fleet.clusterLabels.management.cattle.io/cluster-name } |
Is your feature request related to a problem?
Hi,
currently we are planning to deploy a lot of IoT devices. Only difference is a configMap. While using fleet + kustomize i will have to do sth. like this:
Obviously i don't want to repeat that for xxx customizations for each cluster.
Solution you'd like
Baiscally i want each cluster to have it's own kustomize-dir without having to specify it manually.
Similar to the gobal.fleet variables, but it seems those are not available here?
Alternatives you've considered
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: