-
Notifications
You must be signed in to change notification settings - Fork 745
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
Comments
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.
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.
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.
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.
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.
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.
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.
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. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
/lifecycle frozen |
Yeah.... we REALLY need to improve this. My suggestion is that we add some details on what needs to be done (as explained above) such as:
|
Going to close this for now as honestly, our documentation covers it and this issue is 2 years old. |
It would be great if we output a message relaying the "what next" information after
kompose convert
is run.For e.g.
pvc
object is created, we should display something like "you need to have apv
ready to use this object"Thoughts?
The text was updated successfully, but these errors were encountered: