resources are not prompted
derberg opened this issue · 20 comments
First of all, thanks for the project, this tool is awesome.
I'm using it but from the gifs you provided I understand that it also supports prompting names of actual resources that are available in my cluster. For example if I write "get pods a" it should prompt me all pods that start with "a". Unfortunately it doesn't work for me and I have no idea how to troubleshoot that. Any ideas?
Hi! @derberg
Thank you for using.
Hmm... I want to know your environment. Can you tell me following information?
- OS
- The version of your kubernetes cluster.
- Can you paste the result of
kubectl get pod --all-namespacesif possible.
sure, sorry for not providing those by default:
- macOS Sierra 10.12.5
- latest 1.7 k8s
- list is huge, about 60 of them in total, how is this suppose to help ya? and you want me to do it from kube-prompt or directly the terminal?
this is just few from the kube-prompt:
redis redis-1-kfggz 1/1 Running 0 22h
redis redis-2-27s36 1/1 Running 0 2d
redis redis-3-9dlnl 1/1 Running 0 22h
redis redis-4-pwcrf 1/1 Running 0 2d
redis redis-5-5th9w 1/1 Running 0 22h
redis redis-6-b03cr 1/1 Running 0 2d
tk my-nginx-3021852520-8gck2 1/1 Running 0 22h
ups-broker ups-broker-ups-broker-1523955213-cjgtk 1/1 Running 0 7d
I installed it using brew
+1. doesn't to resource detection here, either. Love the tool so far.
- MacOS Sierra 10.12.6
- 1.6 on server
none of my actual resources come back with prompting....
Now kube-prompt suggests Default namespace pod only. I need to support other custom namespaces.
I'll fix preferentially, because this is a serious problem.
Thanks!
I'm not seeing even the Default namespaces prompted:
Hmm...
@squillace Can you paste the output of get pod --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
default lumbering-eel-maven-648098890-2m06c 1/1 Running 0 10d
default lumbering-eel-maven-648098890-6fdxg 1/1 Running 0 10d
default lumbering-eel-maven-648098890-pxngn 1/1 Running 0 10d
default lumbering-eel-maven-648098890-qftzd 1/1 Running 0 10d
default lumbering-eel-maven-648098890-zhg87 1/1 Running 0 10d
default tiller-deploy-4098450678-pzbwp 1/1 Running 0 10d
kube-system draftd-4057290160-l1j35 2/2 Running 0 10d
kube-system heapster-2708163903-7khfz 2/2 Running 0 14s
kube-system kube-addon-manager-k8s-master-b6eeb91d-0 1/1 Running 0 22d
kube-system kube-apiserver-k8s-master-b6eeb91d-0 1/1 Running 0 22d
kube-system kube-controller-manager-k8s-master-b6eeb91d-0 1/1 Running 0 22d
kube-system kube-dns-v20-77n6l 3/3 Running 0 22d
kube-system kube-dns-v20-w4m64 3/3 Running 0 22d
kube-system kube-proxy-6lnll 1/1 Running 0 22d
kube-system kube-proxy-c08g8 1/1 Running 0 22d
kube-system kube-proxy-cj0hm 1/1 Running 0 22d
kube-system kube-proxy-lr12n 1/1 Running 0 22d
kube-system kube-scheduler-k8s-master-b6eeb91d-0 1/1 Running 0 22d
kube-system kubernetes-dashboard-3995387264-nf8x8 1/1 Running 0 22d
kube-system tiller-deploy-3019006398-z1qkc 1/1 Running 103 11d
BTW, I did the brew install method, if it matters.
also, it's in the default namespace, not Default....
get po --namespace Default returns nothing. :-) Casing for the win.
Thanks. Maybe I understand the cause of your problem.
By the way, can you try the describe command.
I think the describe command is properly working on your environment.
Yes, I can:
Thanks! I'll fix this problem immediately.
that feature alone is fanTASTIC
for me, resources prompt never works, even with describe. I do describe pod ist and there is no prompt with all istio pods that I have on default
full list of get pod --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
catalog catalog-catalog-apiserver-1270003264-xbwrj 2/2 Running 0 7d
catalog catalog-catalog-controller-manager-856269157-np2sk 1/1 Running 0 1d
catalog coupon-deployment-800629525-xq4rw 1/1 Running 0 16h
catalog ingress-nginx-2527469013-tzt5w 1/1 Running 0 6d
catalog limo-deployment-1494902293-9t36s 1/1 Running 0 20h
catalog nginx-default-backend-1226210638-6htv6 1/1 Running 0 1d
catalog qrcode-3671227693-3tf7r 1/1 Running 0 16h
catalog qrcode-deployment-1323837463-mgds1 1/1 Running 0 16h
catalog service-broker-poc-deployment-3949010172-kbjhp 1/1 Running 0 5d
catalog tk-3484351673-plpqq 1/1 Running 0 6d
default builder-1918822101-vxx7c 2/2 Running 0 7d
default echo-log-server-deployment-2471779364-fk6k2 1/1 Running 0 1d
default grafana-1916556110-1zmrh 1/1 Running 0 7d
default istio-egress-664558847-7vqf9 1/1 Running 0 7d
default istio-ingress-1292229662-t9n3k 1/1 Running 0 7d
default istio-mixer-2555573127-x3f5j 1/1 Running 0 7d
default istio-pilot-4143248751-lj1tg 2/2 Running 0 1d
default prometheus-4245872192-6zbw9 1/1 Running 0 7d
default pubsub-1623196080-vhgmg 1/1 Running 0 5d
default pubsub-edge-zuul-3968758917-gq9kw 1/1 Running 0 5d
default pubsub-hermes-consumers-0 1/1 Running 1 1d
default pubsub-kafka-0 1/1 Running 1 1d
default pubsub-management-715056592-l3x6p 1/1 Running 0 1d
default pubsub-redis-2067030810-0p29p 1/1 Running 0 1d
default pubsub-zookeeper-0 1/1 Running 0 1d
default servicegraph-168667903-86nhd 1/1 Running 0 7d
default tk-3484351673-780zg 1/1 Running 1 6d
default tyk-dashboard-1384506445-2g5pb 1/1 Running 0 2d
default tyk-gateway-591818739-r0mcd 1/1 Running 0 2d
default tyk-pump-4222592496-zr6d1 1/1 Running 0 2d
default uaa-644748292-1z5sg 2/2 Running 0 1d
default zipkin-1584795251-zq5ww 1/1 Running 0 7d
kube-system cluster-autoscaler-1563888784-dzn3m 1/1 Running 0 1d
kube-system container-linux-update-agent-1hgtw 1/1 Running 0 8d
kube-system container-linux-update-agent-74zjj 1/1 Running 0 8d
kube-system container-linux-update-agent-dwddl 1/1 Running 0 8d
kube-system container-linux-update-agent-k1p95 1/1 Running 0 8d
kube-system container-linux-update-agent-stkws 1/1 Running 0 8d
kube-system container-linux-update-agent-t09sb 1/1 Running 0 8d
kube-system container-linux-update-operator-835726488-dc8m2 1/1 Running 0 8d
kube-system etcd-operator-1646847766-84cdp 1/1 Running 1 8d
kube-system heapster-3827885079-dlqk8 2/2 Running 0 1d
kube-system kube-apiserver-42h57 1/1 Running 0 8d
kube-system kube-apiserver-6qjbb 1/1 Running 0 8d
kube-system kube-apiserver-z2cl5 1/1 Running 0 8d
kube-system kube-calico-6p9jn 2/2 Running 0 8d
kube-system kube-calico-bq20l 2/2 Running 0 8d
kube-system kube-calico-mxb73 2/2 Running 0 8d
kube-system kube-calico-pwflv 2/2 Running 0 8d
kube-system kube-calico-sznlp 2/2 Running 1 8d
kube-system kube-calico-vzp2t 2/2 Running 0 8d
kube-system kube-controller-manager-4280263814-7npjn 1/1 Running 0 8d
kube-system kube-controller-manager-4280263814-lfmbr 1/1 Running 0 8d
kube-system kube-controller-manager-4280263814-trzmb 1/1 Running 0 1d
kube-system kube-dns-1187388186-q2n48 3/3 Running 0 1d
kube-system kube-dns-1187388186-qvgpz 3/3 Running 0 8d
kube-system kube-dns-autoscaler-637227269-tqcvs 1/1 Running 0 8d
kube-system kube-flannel-1bdpt 2/2 Running 1 8d
kube-system kube-flannel-7lklk 2/2 Running 0 8d
kube-system kube-flannel-9016q 2/2 Running 1 8d
kube-system kube-flannel-bx4m5 2/2 Running 0 8d
kube-system kube-flannel-m5vd9 2/2 Running 1 8d
kube-system kube-flannel-wpgn2 2/2 Running 0 8d
kube-system kube-proxy-22wv1 1/1 Running 0 8d
kube-system kube-proxy-341wl 1/1 Running 0 8d
kube-system kube-proxy-lf9tj 1/1 Running 0 8d
kube-system kube-proxy-m6xg3 1/1 Running 0 8d
kube-system kube-proxy-q99s1 1/1 Running 0 8d
kube-system kube-proxy-z0rg0 1/1 Running 0 8d
kube-system kube-scheduler-559132610-0dxrz 1/1 Running 0 1d
kube-system kube-scheduler-559132610-4xwcc 1/1 Running 0 8d
kube-system kube-scheduler-559132610-6fp19 1/1 Running 0 8d
kube-system kubernetes-dashboard-3313488171-2njp9 1/1 Running 25 8d
kube-system pod-checkpointer-gsbcr 1/1 Running 0 8d
kube-system pod-checkpointer-gsbcr-ip-10-64-129-220.eu-central-1.compute.internal 1/1 Running 0 8d
kube-system pod-checkpointer-nfdtg 1/1 Running 0 8d
kube-system pod-checkpointer-nfdtg-ip-10-64-130-107.eu-central-1.compute.internal 1/1 Running 0 8d
kube-system pod-checkpointer-wjs1l 1/1 Running 0 8d
kube-system pod-checkpointer-wjs1l-ip-10-64-129-59.eu-central-1.compute.internal 1/1 Running 0 8d
kube-system tiller-deploy-1884622320-c73bj 1/1 Running 0 8d
mongo mongodb-2789618937-wlzk9 1/1 Running 0 2d
redis redis-1-kfggz 1/1 Running 0 1d
redis redis-2-27s36 1/1 Running 0 2d
redis redis-3-9dlnl 1/1 Running 0 1d
redis redis-4-pwcrf 1/1 Running 0 2d
redis redis-5-5th9w 1/1 Running 0 1d
redis redis-6-b03cr 1/1 Running 0 2d
tk my-nginx-3021852520-8gck2 1/1 Running 0 1d
ups-broker ups-broker-ups-broker-1523955213-cjgtk 1/1 Running 0 7d
Yeah, @derberg.
The cause of your problem related to namespace setting. So I understand describe <podname> completion is not properly working in your environment.
Your problem is different with the squillace's problem.
I'll fix both of problems.
Thanks.
squillace's problem which kubectl get <podname> doesn't properly working is already fixed at latest revision of master branch.
ACK. brew isn't update, but I may go back and clone.
Back. OK, so now brew has updated and exit works properly as well as get po, as in the following:
However, other commands do not autosuggest:
I confirm,
exit works like a charm
autosuggest not