-
Notifications
You must be signed in to change notification settings - Fork 101
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
Default to current namespace? (or via --ns
)
#33
Comments
Hi @rcoup, thanks for the input! I agree that the I think something like the following would be a reasonable approach:
Let me know if you have any thoughts on this.
Thanks for pointing that out, these should have the same behavior. |
We mostly use namespaces for logical app separation, so (virtually) everything relevant is in the same namespace. But I guess that can be different for everyone. I'm not that keen on another flag for So:
|
Me neither, but if it's easy to use and not confusing, I'd go for it. At the end of the day, this can all be done with scripting, but it's nice to have some things baked in instead of this: alias kailc='kail --ns $(kubectl config view -o jsonpath="{.contexts[?(.name==\"$(kubectl config current-context)\")].context.namespace}") ' I frankly don't even know if it's possible to get the current namespace from
I was thinking it'd default to |
I think that's the logic I wrote down? If you specify ns/current-ns then you don't get "all" anymore, and anything you do specify should override the ignore list anyway. |
👍 pre-coffee parsing never works for me. Thanks for the input! |
Currently
kail
with no arguments matches every pod in the cluster — personally I think this should be the current namespace, there's so many system pods and their logs aren't usually relevant to day to day application work. Not sure how you feel about changing that default?Otherwise, it'd be nice for
kail --ns
(ie. with no namespace) to default to the current namespace. Currently,--ns
matches all namespaces, and--ns=
matches nothing.The text was updated successfully, but these errors were encountered: