Closed shihyuho closed 1 year ago
I don't know why this is so necessary tbh, can you explain? I think we should support only one format, and if there's strong preference (which I am not understanding), let's break and switch to that syntax instead.
Since kubectl
supports both formats, I would expect the same for this plugin, which is what happened last week when I downloaded the plugin for the first time.
I think it's natural for anyone to use the Kubernetes knowledge he/she has to the plugin, so of course it's not "so necessary", but I guess it's definitely a "nice to have" feature
btw, I love the plugin :grinning: I'm building my CRDs, it really helped me to track down the objects I create.
40, accept both KIND NAME or KIND/NAME form to specify the Kubernetes object
e.g.
kubectl tree deployment my-app
,kubectl tree deployment/my-app