kubectl resources autocompletion

[giolf]

Describe the solution you'd like?

Currently warp allows to autocomplete kubectl commands like:
kubectl get or kubectl describe

However it doesn't provide resources autocompletion, for example:
if you type: kubectl describe pod -n my-namespace and then if you press TAB it doesn't show you the list of the pods in that particular namespace.

I tried to setup on my .zshrcfile the following instruction:

# kubectl config
source <(kubectl completion zsh)

and on iTerm2 it works, but not in warp.

I think it would be super cool to provide this extra layer of autocompletion (similarly to the autocompletion warp offer with git)

How important is this feature to you?

4

[dannyneira]

Thanks for this feature request!

To anyone else interested in this feature, please add a :+1: to the original post at the top to signal that you want this feature, and subscribe if you'd like to be notified.

[pierre-mike-pge]

+1

[cedi]

+1

[giolf]

+1

[vlad-artyomov]

+1

[macro-dadt]

+1

[muneebshahid]

+1

[pavan2004it]

+1

[piavgh]

+1

[piavgh]

After having this feature, I will remove iTerm2 😄

[lummie]

+1

[RapidIE]

+1
+10
+1000 =)

[yevhenvolchenko]

+1

given kubernetes has extensible api having resources autocomplete is very important; native kubectl autocomplete has it for a reason!

[unbreakabl3]

+1 for that functionality

[vincent-at-trust]

+1

[lkoniecz]

+1

[pavan2004it]

+1

[gomgomshrimp]

+1
This feature is very important.
People who often work with Kubernetes avoid warp because it doesn't support this feature.

[Elias-Chairi]

+1

[ovstuckrad]

Definitely need this to use Warp!

[ErlendFax]

+1

[clementblaise]

+1

[MiddleCloud]

+1

[domechn]

+1

[hreinking]

+1, a deal-breaker for me, and loving Warp so far.

[nianyush]

+1

[ebenezar-mccoy]

+1

[rayanebel]

+1

[fatalwithin]

+1

[imans777]

+1

[JonasHess]

+1

[lieberlois]

+1

[valdirjunior011]

+1

[jzuijlek]

+1

[noahzweben]

Hi all - I'm Noah, a PM at Warp. We finally have a Warp demo build that has support for kubernetes completions!

Since we don't use kubernetes at Warp, we're looking for people who want to test this in the wild! If you're interested in trialing kubernetes completions before we publicly release it, please email me at noah@warp.dev

It adds support for suggesting:

• k8s resources
• global options (e.g. kubectl options)
• when --namespace and/or --kubeconfig are supplied, scope down suggestions to the specified namespace/kubeconfig

[that70schris]

is it possible to add support for kubecolor as well?

[dannyneira]

Good news folks! The latest version of Warp now supports additional kubectl completions, including suggestions for resources, global options, and namespaces!

Closing as completed, but please feel free to let us know if any bugs by opening a new GitHub issue.

[Pger-Y]

Cool feature！！！Have been used for several days, but there is still some suggestions,only typing kubectl there is k8s-context showing in prompt,i think it can be shown all the time,or type k,because we all alias kubectl as k :(
Thanks :)

[schabrolles]

Yes, that's a good step. Thank hope to have openshift cli soon (oc) which is based on kubectl.

[zachbai]

@that70schris saw you opened #3922 -- I have that on my slate so should be able to get to it within the coming weeks. Will update that issue when available

[imans777]

Cool feature！！！Have been used for several days, but there is still some suggestions,only typing kubectl there is k8s-context showing in prompt,i think it can be shown all the time,or type k,because we all alias kubectl as k :( Thanks :)

You can use a workaround here, there's a feature in Warp: "Expand aliases as you type". when you enable this, whenever you type k it automagically converts it to kubectl and then you can have all kubectl autocompletion active! This is also useful for other commands or aliases that you've set.

[AdamGold]

Hey, there's a problem with auto completing kubectl logs -- it doesn't autocomplete the resource name until you do kubectl logs pod ..... but that's not how kubectl command works with logs, it expects the resource name right after kubectl logs.

[lkoniecz]

alias k='/opt/homebrew/bin/kubectl'

does not seem to be working with aliases, or is it only me?

regards

[rasifdo]

finally one of the most awaited features! hoping the team fixes autocompletion for 'k logs' as @AdamGold mentioned

[dannyneira]

@lkoniecz Yes, the alias should work, even with Alias Expansion disabled.

[lkoniecz]

@dannyneira I don;t think I need to disable that - it still works with kubectl.

[imans777]

just to make sure this is not missed, I'm copying my comment about my experience on kubectl missing autocompletions here too:
#652 (comment)

[nizametdinovcrx]

Hey, there's a problem with auto completing kubectl logs -- it doesn't autocomplete the resource name until you do kubectl logs pod ..... but that's not how kubectl command works with logs, it expects the resource name right after kubectl logs.

Is this resolved?

[zcl0621]

@nizametdinovcrx also not support...

[cx2c]

I need type external pod to complet pod name. but kubectl logs -n xxx pod xxxx is not a kubectl command

[yura-kutsiy]

Join the open issue (related kubectl log autocompletion feature) and leave your thumbs up.

#3958

[rubengmurray]

Doesn't work for me at all in conjuction with ohmyzsh

[mostafamoq]

need this future , kubectl-autocomplete not working on warp over zsh ohmyzsh

[kopaygorodsky]

kubectl logs still does not work as some other items. Would be nice to be able to disable autocomplete for certain binaries.

[ghost]

any updates on the resource name auto completion part, this is the only feature preventing me from never using terminal again. Currently needing to use an extra get pod, service... command just to get the pod name to be used in the log or describe command is inconvenient.

[rubengmurray]

This needs to happen. It's my only complaint with warp.

[mschaefer-gresham]

Please add this feature and feature request 3978 at the same time. Thank you!