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

export as helm chart(s) #4432

Open
langdon opened this issue Feb 12, 2021 · 3 comments
Open

export as helm chart(s) #4432

langdon opened this issue Feb 12, 2021 · 3 comments
Labels
kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@langdon
Copy link

langdon commented Feb 12, 2021

/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?

  • nothing equiv exists and it would help migrations
  • learning something new (like how to write helm charts) is easier when the "example" is based on something you know (like my project)

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.

@openshift-ci-robot openshift-ci-robot added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label Feb 12, 2021
@kadel
Copy link
Member

kadel commented Feb 16, 2021

👍 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.

@openshift-bot
Copy link

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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 17, 2021
@dharmit dharmit removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 17, 2021
@kadel
Copy link
Member

kadel commented May 17, 2021 via email

@openshift-ci openshift-ci bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label May 17, 2021
@rm3l rm3l added this to odo Project Oct 3, 2022
@rm3l rm3l moved this to To Do 📝 in odo Project Oct 3, 2022
@rm3l rm3l removed the status in odo Project Oct 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Status: No status
Development

No branches or pull requests

5 participants