-
Notifications
You must be signed in to change notification settings - Fork 130
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
Explore ownership between built-in and custom resources #36
Comments
It might be because it's cluster-scoped. Gotta check out the code, I don't think we'd have anything explicitly prevents this. |
Actually yeah in query.go we explicitly skip non-namespaced CRDs. I am trying to remember why but there must've been a reason. |
Thanks for checking @ahmetb I'd love to know what was the reason for skipping non-namespaced CRDs. IMO Having them displayed by tree would be very useful. |
Indeed! It works with the -A flag. Awesome @ahmetb . Thank you for a prompt reply and this amazing plugin 💪
|
I do have a custom cluster-scoped resource
CISKubeBenchReport
that I'm associating with a built-inNode
object. However, when I run$ kubectl tree node <node name>
I cannot see such relationship displayed.My objects, stripped out of nonessential properties, look as follows:
Is there anything that I'm missing in my onwerReferences config or is that kubectl-tree that cannot handle such config?
The text was updated successfully, but these errors were encountered: