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

Use upstream helm instead of rancher/helm #302

Conversation

rohitsakala
Copy link
Member

Please check the JIRA issue for more information.

Summary

  • Upstream helm has all the features that rancher/helm has. So, moving to upstream helm.

@rohitsakala rohitsakala force-pushed the remove-usage-of-forceadopt-flag-of-helm-fork-in-catalogv2-package branch from 4d936f8 to 5c47beb Compare January 17, 2025 22:16
@rohitsakala rohitsakala changed the title Remove usage of forceadopt flag of helm fork in catalogv2 package Use upstream helm instead of rancher/helm Jan 17, 2025
@mallardduck
Copy link
Member

@rohitsakala - Is this something you expect we can backport, or is this just intended for 2.11? Currently main in this repo is lagging a little and still focused on 2.10. But if it's meant for 2.11 I can setup 2.10 branches.

@rohitsakala
Copy link
Member Author

@mallardduck This is currently postponed. I will close this PR.

@rohitsakala rohitsakala deleted the remove-usage-of-forceadopt-flag-of-helm-fork-in-catalogv2-package branch January 24, 2025 01:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants