-
Notifications
You must be signed in to change notification settings - Fork 56
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
More powerful resource matching (ERRO[0005] determine requested resource: no matches for ...) #139
Labels
bug
Something isn't working
Comments
Interesting, thanks for reporting! Can you check if other CRDs have the same problem? Also, please enable verbose logging to make debugging easier. I don't have access to a gs cluster :) |
Same problem with other CRDs.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a cluster with a CRD named
Organization
(long name:organizations.security.giantswarm.io
), the following command works fine:However, when I use the full CRD name instead, this happens:
I expected to be able to use the full name, like it's the case with
kubectl get <resource>
.The text was updated successfully, but these errors were encountered: