-
Notifications
You must be signed in to change notification settings - Fork 13
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
Include Helm Charts in release process #87
Comments
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. |
This is still relevant. |
A user pointed out that we're still pinning to Submariner 0.7.0 in all submariner-operator chart versions, including the 0.8.1 and 0.9.0-m2 releases and the current devel. |
Maybe this is something we should prioritize for 0.9 @mkolesnik @mangelajo @tpantelis @skitt @nyechiel? It seems to me like we should have this part of the release hammered out before we consider Submariner supportable. |
I noticed that too when I fixed the release job. I was going to raise the topic but then slipped my mind |
Well release already tags submariner-charts repo, it can also update
whatever is necessary there i guess
…On Thu, Apr 8, 2021 at 12:11 AM Thomas Pantelis ***@***.***> wrote:
A user pointed out that we're still pinning to Submariner 0.7.0 in all
submariner-operator chart versions, including the 0.8.1 and 0.9.0-m2
releases and the current devel.
https://github.com/submariner-io/submariner-charts/blob/v0.8.1/submariner-operator/values.yaml#L14
https://github.com/submariner-io/submariner-charts/blob/v0.9.0-m2/submariner-operator/values.yaml#L37
https://github.com/submariner-io/submariner-charts/blob/devel/submariner-operator/values.yaml#L37
I noticed that too when I fixed the release job. I was going to raise the
topic but then slipped my mind
--
Regards,
Mike
|
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. |
@Jaanki brought this up on a dev call recently, highlighted that we're still not updating the version in submariner-charts. Is this something we want to try to do in 0.12, @mkolesnik? I just noticed it's in backlog/backlog. (also I might be able to help with this, if this is a "good-first-issue" for the releases project) |
I think this is the step we want to automate: submariner-io/submariner-charts#182 |
Here's another, from a user: submariner-io/submariner-charts#172 |
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. |
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 do this to some extent now, but there's still more to do:
(should all be 0.16 now) |
This was implemented in 0.16. |
There's currently no mention of Helm in the releases repo or the release process docs.
We should connect the Helm Charts release automation with the automation here, and document the process on the website.
The text was updated successfully, but these errors were encountered: