-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Make cilium status
output more succinct by default
#2821
Conversation
test-me-please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also add a --brief
option which prints the overall status on a single line? We need this for the Kubernetse healthcheck.
@tgraf sure, do you have an example of how that output should look? From a quick search, it looks something like we need this on success:
Or this on failure:
|
ACK |
Since we are touching this can we also change it to something like
Also, I'm assuming you are changing this because of the number of allocated IP addresses. Can we use @ianvernon 's IP "coalesce" functionality to present the IPs in CIDRs when possible? |
@aanm looks good, one comment:
^ Writing |
I think so, we were already showing up all nodes in the cluster with |
@aanm Seems like a reasonable idea. I'll play around with it a bit. Do we really need node information like allocrange for all other nodes in |
Here's a quick mockup: When a node is unhealthy, regular output (only print unhealthy nodes):
With all nodes healthy, option to print all health details:
When cilium-health isn't up:
|
@joestringer I was only thinking for the current node but we have the alloc range for all nodes in the |
@aanm right, that's what the current output in |
9bcd89a
to
dd92755
Compare
Added patch for cilium status --brief
Frame controller output in terms of how many are OK, rather than how many are failing. Signed-off-by: Joe Stringer <joe@covalent.io>
Introduce three new arguments to 'cilium status': * allAddresses: Print all addr allocations (default: print only the count) * allNodes: Print all known nodes (default: only print localhost info) * verbose: Equivalent to --all-addresses --all-controllers --all-nodes This ensures that by default in large environments, 'cilium status' will not flood the terminal of the person trying to get information, but still allows more information to be gathered on demand. Signed-off-by: Joe Stringer <joe@covalent.io>
Fixes: cilium#2749 Signed-off-by: Joe Stringer <joe@covalent.io>
The new `--brief` argument prints a single line summary of the status which prints either "OK" or "error: ...", which prints only one of the errors currently reported in the system, with preference in this order: * Cilium daemon * Container Runtime * Kvstore * Kubernetes * Cilium-health daemon * Controllers inside Cilium daemon Signed-off-by: Joe Stringer <joe@covalent.io>
This will be used by an upcoming commit to report the max number of IPs that may be allocated by cilium. Signed-off-by: Joe Stringer <joe@covalent.io>
Signed-off-by: Joe Stringer <joe@covalent.io>
0377a7b
to
876851d
Compare
test-me-please |
Due to cilium#2821 run the SRv6 datapath e2e tests only with SID Manager disabled.
Add
--verbose
mode and some extra options to choose how much output you want from the cilium status API. Gather the verbose output in bugtool. Fold in a minor change to phrase controller states in terms of success rather than failure.Example output with this series:
There's also this command for a brief, one-line summary: