-
Notifications
You must be signed in to change notification settings - Fork 27
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
Epic: Helm as first-class deploy tool #138
Comments
Discussions on the Automation Sync today included starting from scratch with the Helm carts. That might be the quickest path to a quality result (so much needs to be changed with the current charts) and would allow us a good Helm learning opportunity along the way. |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
We should make sure the release process with the GH page works for versioned releases, branches. |
This has been discussed on the issue scrub meeting and decided to close for now. |
We've primarily focused on using
subctl
to deploy the Operator so far. With few Helm jobs running in other repos, we frequently break Helm deployments and don't know about it quickly.My understanding is that we want to support Helm at last as much as subctl. We've also seen a substantial number of K8s users start trying Submariner using Helm.
The end goal here is to use Helm+Operator as the default deployment tool and for Helm to be part of the automated release process.
Bugs:
Features:
charts/
directory Move all charts into /charts dir #88Testing:
Release:
Docs:
The text was updated successfully, but these errors were encountered: