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
When using karmor probe the node information takes the most time to load. While the node value is very important and is very helpful during debugging, it is something that one might not want to stdout every time one runs karmor probe. When you're running a large cluster, then getting to Armored up pods is taking a long time.
One should get to the Armored up pods directly and if something is breaking then they should take a look at node related information.
Proposed Solution:
We can introduce a flag that will only print armored up pods section (preferred) OR
We can introduce a --node=<node-name> flag that will only print the respective node specific information and if set to false it will not print any node related information.
The text was updated successfully, but these errors were encountered:
When using
karmor probe
the node information takes the most time to load. While the node value is very important and is very helpful during debugging, it is something that one might not want tostdout
every time one runskarmor probe
. When you're running a large cluster, then getting toArmored up pods
is taking a long time.One should get to the
Armored up pods
directly and if something is breaking then they should take a look at node related information.Proposed Solution:
armored up pods
section (preferred) OR--node=<node-name>
flag that will only print the respective node specific information and if set tofalse
it will not print any node related information.The text was updated successfully, but these errors were encountered: