-
Notifications
You must be signed in to change notification settings - Fork 243
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
export as helm chart(s) #4432
Comments
👍 This would be a nice feature. Problem is that currently, odo can't produce images that could be used in Helm Charts :-( Devfile v2 will need to be able to describe the image build process (currently it is just describing the application build). This is currently being discussed and designed in devfile/api#51 Once we have a runnable image we can look into generating Helm Charts. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
This is still valid.
Once it is possible to define outerloop in Devfile v2 we will look into
ways how can use it to generate Helm Chart.
/remove-lifecycle stale
/lifecycle frozen
…On Mon, 17 May 2021 at 15:29, OpenShift Bot ***@***.***> wrote:
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually
close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4432 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAN65QJMBDFHVXRZVS2S43TOEK2PANCNFSM4XRMUVRA>
.
|
/kind feature
Which functionality do you think we should add?
I would love to be able to take an existing project/namespace and export it as a helm chart.
Why is this needed?
The reason for the "(s)" is because I am not sure if it would be better to export each service as a helm chart then tie them together or one big helm chart. I lean toward the former but maybe that could be "version 2" after the latter.
The text was updated successfully, but these errors were encountered: