The Wayback Machine - https://web.archive.org/web/20201231223909/https://github.com/kubernetes/kompose/issues/345
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

Show "next steps" after kompose convert #345

Open
concaf opened this issue Dec 27, 2016 · 3 comments
Open

Show "next steps" after kompose convert #345

concaf opened this issue Dec 27, 2016 · 3 comments

Comments

@concaf
Copy link
Contributor

@concaf concaf commented Dec 27, 2016

It would be great if we output a message relaying the "what next" information after kompose convert is run.

For e.g.

  • If a pvc object is created, we should display something like "you need to have a pv ready to use this object"
  • In case of a missing port, "you might want to expose this service manually since kompose could not detect a port"

Thoughts?

surajnarwade added a commit to surajnarwade/kompose that referenced this issue Apr 3, 2017
Partially resolve kubernetes#376 and kubernetes#345
Added warning, such that PV should be created before PVC or
if dynamic provision is there, no need to create PV.
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Apr 3, 2017
Partially resolve kubernetes#376 and kubernetes#345
Added warning, such that PV should be created before PVC or
if dynamic provision is there, no need to create PV.
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Apr 4, 2017
Partially resolve kubernetes#376 and kubernetes#345
Added warning, such that PV should be created before PVC or
if dynamic provision is there, no need to create PV.
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Apr 4, 2017
Partially resolve kubernetes#376 and kubernetes#345
Added warning, such that PV should be created before PVC or
if dynamic provision is there, no need to create PV.
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Apr 13, 2017
Partially resolve kubernetes#376 and kubernetes#345
Added warning, such that PV should be created before PVC or
if dynamic provision is there, no need to create PV.
qujinping pushed a commit to qujinping/kompose that referenced this issue Apr 25, 2017
Partially resolve kubernetes#376 and kubernetes#345
Added warning, such that PV should be created before PVC or
if dynamic provision is there, no need to create PV.
cdrage added a commit to cdrage/kompose that referenced this issue May 17, 2017
Partially resolve kubernetes#376 and kubernetes#345
Added warning, such that PV should be created before PVC or
if dynamic provision is there, no need to create PV.
@cdrage
Copy link
Member

@cdrage cdrage commented Jul 19, 2017

I agree with this, @surajnarwade has updated this in cdrage@f88d489 however, I still think there could be some improvement.

Tools such as Helm have a lot of logging output that describes all the steps after launching / using Helm.

@fejta-bot
Copy link

@fejta-bot fejta-bot commented Jan 1, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@cdrage
Copy link
Member

@cdrage cdrage commented Jan 2, 2018

/lifecycle frozen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.