-
Notifications
You must be signed in to change notification settings - Fork 26
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
Template-Based Helm Chart Versioning in ClusterProfile Using Labels #794
Comments
Thank you @emreberber I will think a little more on this tomorrow before confirming, but I believe this should be easy to implement. But again, I will spend some time on it before confirming it. Thanks for suggesting this. |
Thank you in advance @gianlucam76 🙏🏻 🚀 |
Could you assign this to me, I would be more than happy to help |
Hi @DanaIzadpanah thank you. This is kinda of taken care of by this If you see any other issue you would like to help with, I would be more than happy to assign it to you. Thank you so much! |
Yes I will definitely let you know :) |
Thank you @DanaIzadpanah Not sure if this is interesting to you, but if so it would be great to:
Thank you! |
Currently, ClusterProfile in Sveltos allows defining a fixed chartVersion for Helm charts across clusters that match a clusterSelector. However, in complex environments where clusters vary in Kubernetes version, region, or other metadata, a single chartVersion may not meet compatibility or regional deployment requirements. A templating approach, where chart versions (or other configurations) can dynamically adjust based on metadata labels, would offer more flexible and efficient management.
Example Use Case:
For instance, if clusters have metadata labels such as k8s-version, region, or env, ClusterProfile could use these to set the chartVersion or other parameters automatically:
The text was updated successfully, but these errors were encountered: