CLI log could use some kind of feedback when waiting for pod to spin up #1283
Labels
Comments
This was referenced Feb 19, 2020
lburgazzoli
added
area/ux
|
Starting to poke around the binaryb go code so alright if I have a look at this? |
phantomjinx
added a commit
to phantomjinx/camel-k
that referenced
this issue
Oct 29, 2020
…r to install * Sets up a polling prior to the complete install of an integration * First report whether it finds the integration * Assume it finds an integration then determine its status * If it gets to Building Kit (which can take a while) then find the associated IntegrationKit and report its status * Finally return to the scraping of the log once the integration is up and running
|
Create PR #1793 |
phantomjinx
added a commit
to phantomjinx/camel-k
that referenced
this issue
Oct 29, 2020
…r to install * Sets up a polling prior to the complete install of an integration * First report whether it finds the integration * Assume it finds an integration then determine its status * If it gets to Building Kit (which can take a while) then find the associated IntegrationKit and report its status * Finally return to the scraping of the log once the integration is up and running
nicolaferraro
pushed a commit
that referenced
this issue
Nov 2, 2020
…nstall * Sets up a polling prior to the complete install of an integration * First report whether it finds the integration * Assume it finds an integration then determine its status * If it gets to Building Kit (which can take a while) then find the associated IntegrationKit and report its status * Finally return to the scraping of the log once the integration is up and running
Closed
|
This issue has been automatically marked as stale due to 90 days of inactivity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're shifting over to using
kamel log [integration]instead ofkubectl logs-f [podname]for displaying logs in the VS Code extension and I've noticed that while waiting for the kit to build and the first integration pod to deploy, there is just... nothing. Without any kind of user feedback, some users may wonder if the integration will ever spin up.It's great once it gets started and does everything we could want, including shifting to a different pod after an update and redeploy to avoid getting stale, which is something that occurred frequently when we were using the kubectl logs approach.
Would it be possible to display something like
Waiting for [integration] container to start...or perhaps have some message displayed to the user (anything really) indicating that work is going on behind the scenes?Invoking the CLI and then waiting on the log takes a very long time initially and it would be nice to possibly show something to the user during that period. Even a simple "..." showing that it's still chugging away waiting for containers to get going would be preferable to dead silence I think.
The text was updated successfully, but these errors were encountered: