Get command failed: error: there is no need to specify a resource type as a separate argument

When expanding any pod on a node I get the following error:

Get command failed: error: there is no need to specify a resource type as a separate argument when passing arguments in resource/name form (e.g. 'kubectl get resource/<resource_name>' instead of 'kubectl get resource resource/<resource_name>'

Error loading document: Error: cannot open k8smsx://loadkubernetescore/pod-kube-system%20%20%20%20%20%20%20%20%20%20%20%20coredns-9bc57ddff-vnrft.yaml?ns%3Dall%26value%3Dpod%2Fkube-system%20%20%20%20%20%20%20%20%20%20%20%20coredns-9bc57ddff-vnrft%26_%3D1611860122528. Detail: Unable to read file 'k8smsx://loadkubernetescore/pod-kube-system            coredns-9bc57ddff-vnrft.yaml?ns=all&value=pod/kube-system            coredns-9bc57ddff-vnrft&_=1611860122528' (Get command failed: error: there is no need to specify a resource type as a separate argument when passing arguments in resource/name form (e.g. 'kubectl get resource/<resource_name>' instead of 'kubectl get resource resource/<resource_name>'
)

Repro:

• Expand cluster
• Expand Nodes
• Expand a node
• Expand a pod (Ex : coredns)

Expected: Not sure, first time using this extension

Actual: UX spins for a while, then creates a sub-node under the pod with the text ‘Error’ and VSCode pops the above error messages.

Tested with these kubectl/AKS versions:

kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-13T13:28:09Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.8", GitCommit:"c86ad89b8715ed17fd55b87cbb2888ccc6fa9878", GitTreeState:"clean", BuildDate:"2020-09-25T01:53:27Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

[itowlson]

Fix is out for review and should be in the next release. Thanks for the precise and methodical bug report and repro instructions - this really helped to nail it quickly.

[itowlson]

Okay #797 introduced a bug in outputUtils.ts > findPositionHeaders (line 31) where it would get the wrong position for any column whose header was a substring of an earlier header. This kubectl output has NAMESPACE followed by NAME so we incorrectly start the NAME column at the position of the NAMESPACE column and this truncates the NAMESPACE column. This should be an easy fix - fingers crossed.