Skip to content
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

Allow more conventional --namespace / -n flag placement #8

Closed
mcandre opened this issue Sep 23, 2021 · 1 comment
Closed

Allow more conventional --namespace / -n flag placement #8

mcandre opened this issue Sep 23, 2021 · 1 comment

Comments

@mcandre
Copy link

mcandre commented Sep 23, 2021

Hey, I don't know if this is a problem with kpexec specifically, or more likely the kubectl plugin system. But it's annoying to not be able to use --namespace / -n before the pexec subcommand.

When operating on a lot of different namespaces, it is practical to declare the namespace early rather than late in kubectl commands.

@ssup2
Copy link
Owner

ssup2 commented Nov 6, 2021

@mcandre I've known this issue. But this is the limitation of kubectl. This is one of the reasons why I developed kpexec as a standalone binary before kubectl plugin.

@ssup2 ssup2 closed this as completed Nov 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants