-
Notifications
You must be signed in to change notification settings - Fork 28
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
No resources returned in v1.3.4 #93
Comments
Can you also share your kubernetes version? I bumped the k8s version in 1.3.3 and maybe that creates some incompatibilities. |
|
v1.3.3 works for me but not v1.3.4. I believe a previous commit broke Specifically, all booleans in the scope logic were flipped except this one: 93a2c9f#diff-2c846caea57b2b1d6e49c6417f337625R214 I've opened a pull request with a fix: #98 |
Thanks, latest version is now working for me 👍 |
The praise goes to @busser who looked into this. |
Describe the bug
No resources are being returned in the latest version of the krew plugin.
To Reproduce
Steps to reproduce the behavior:
DEBU[0000] Set log-level to debug DEBU[0001] Resources to fetch: [] DEBU[0001] Initial fetchResourcesBulk done (0s) DEBU[0001] Fetch resources incrementally DEBU[0001] Requests done (elapsed 0s) WARN[0001] No resources found, are you authorized? Try to narrow the scope with --namespace. FATA[0001] no resources found
Expected behavior
I expected too see the same resources I could in v1.3.2
Screenshots

Desktop (please complete the following information):
ketall version --full
:Additional context
Exact same command and kubectl version worked fine for version 1.3.2, seems to be a bug.
The text was updated successfully, but these errors were encountered: