You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, when I select multiple pods with Click and use the logs command, it executes multiple logs commands sequentially instead of giving a merged output.
It would also be nice to be able to select a deployment to request logs for instead of having to select multiple pods (based on a regex or label).
And lastly, if such a merging logs command existed, it would be good if it had the --prefix option of kubectl with some color coding added to differentiate the different pods.
The text was updated successfully, but these errors were encountered:
This is a cool idea. Does kubectl actually merge the logs though? In my testing it just gives you sequential logs from each matching pod, but does allow prefixing them.
So just to clarify, this is more about merging when doing -f so that you can follow logs from more than one pod?
In my experience kubectl does seem to merge logs fine, but previous (non-followed) logs appear to be inaccurately ordered. When following logs the kubectl logs do make more sense though.
When you have multiple replicas in your deployment you often want to see the logs of all pods at once. With kubectl I would use something like this:
However, when I select multiple pods with Click and use the logs command, it executes multiple logs commands sequentially instead of giving a merged output.
It would also be nice to be able to select a deployment to request logs for instead of having to select multiple pods (based on a regex or label).
And lastly, if such a merging logs command existed, it would be good if it had the
--prefix
option of kubectl with some color coding added to differentiate the different pods.The text was updated successfully, but these errors were encountered: