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

[Bug] not using current namespace on macosx #13

Closed
fredleger opened this issue Aug 10, 2019 · 1 comment · Fixed by #15
Closed

[Bug] not using current namespace on macosx #13

fredleger opened this issue Aug 10, 2019 · 1 comment · Fixed by #15
Labels
enhancement New feature or request

Comments

@fredleger
Copy link

Describe the bug
Need to specify namespace to have results on macosx

To Reproduce
Steps to reproduce the behavior:

  1. kubectl grep pods nginx
  2. kubectl grep pods nginx -n demo

Expected behavior
I would have thought that it would use the current NS

Screenshots

Environment (please complete the following information):

  • Operation System: macOS
  • Kubernetes Version 1.12.9
    Kubectl Version v1.14.3

Additional context
NA

@guessi guessi added the enhancement New feature or request label Aug 10, 2019
@guessi
Copy link
Owner

guessi commented Aug 10, 2019

@fredleger Thanks for report.

You're right, it should respect the value of the namespace value in ~/.kube/config. I will mark this report as enhancement, and fix it later, but there's no ETA for the fix. If this feature matter to you, maybe you can try to create a pull-request for the fix :octocat: FYI, you may find the source code HERE.

Story behind, while I was designing this tool, my initial thought was that having namespace defined explicitly would be safer, especially for production environment. For now, please take this a hard limitation.

guessi added a commit that referenced this issue Nov 14, 2019
Fixes: #13

Signed-off-by: guessi <guessi@gmail.com>
guessi added a commit that referenced this issue Nov 14, 2019
Fixes: #13

Signed-off-by: guessi <guessi@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants