-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add Auto-Upgrade Feature for Seamless Chart Deployment and Version Management #241
Comments
Hey @aviorma, thanks for raising this! |
Hey @aviorma, we picked this up in the past couple of days. We added a section to the resolve-version.mp4You can try it yourself by installing the RC version we created by running the command below: kubectl apply -f https://raw.githubusercontent.com/cyclops-ui/cyclops/v0.5.0-rc.1/install/cyclops-install.yaml &&
kubectl apply -f https://raw.githubusercontent.com/cyclops-ui/cyclops/v0.5.0-rc.1/install/demo-templates.yaml Let me know what you think and if this would help your team |
Problem Statement:
Our team aims to streamline the deployment process by utilizing this tool to effortlessly deploy charts and seamlessly upgrade versions as soon as they are available in the Helm repository.
Proposed Solution:
Integrate a feature that enables users to auto-upgrade the chart to the latest version with the click of a button, similar to the functionality offered by flux2 (Gitops).
Alternative Solutions:
Manual version checks and upgrades can be cumbersome and prone to human error. Automating this process would significantly reduce the workload and ensure timely updates.
Implementing a notification system to alert users about new chart versions could also be beneficial, but it may not be as efficient as an automated upgrade option.
Additional Context:
By incorporating this auto-upgrade feature, users can maintain their deployments effortlessly, staying up-to-date with the latest features and fixes without manual intervention. This enhancement would greatly enhance the efficiency and usability of the tool.
The text was updated successfully, but these errors were encountered: