jqp VS kubectx

You may be familiar with some utilities that provide this interactivity, like jqp, but these come with their own downsides, namely subtle bugs due to the re-implementation of the original JQ in language X, but also they are additional dependencies you have to track and install for your platform architecture and OS/distribution.

Jqp: https://github.com/noahgorstein/jqp (for more complex jq stuff)

Also check out jqp (jq REPL) for when you need a few tries to get the right jq selector: https://github.com/noahgorstein/jqp

Looks a bit like fzf combined with jq.

jqp the Text User Interface for playing about with jq might help a bit.

You can have your input JSON terminal left, the output post jq terminal right and interactively edit your jq script elements above.

( based upon the Go implementation of jq )

See: https://github.com/noahgorstein/jqp

I also showed using a TUI wapper around `jq` called `jqp` https://github.com/noahgorstein/jqp which can be nice when iterating on a `jq` filter

Jqp – A TUI playground for exploring jq\ (22 comments)

kubectx: brew install kubectx

default is where any actions which require a namespace will go into if one is not explicitly defined in a default setup (tools such as kubens can alter this behavior). In the context of Jenkins, namespaces are a useful way to allow isolation of individual Jenkins instances that want to utilize the same Kubernetes cluster. Creation of a namespace is a simple option to kubectl:

Here you go: https://github.com/ahmetb/kubectx and https://kubecm.cloud/

check out kubectx/kubens https://github.com/ahmetb/kubectx very handy tool to permanently switch context/namespace

kubectx + kubens v0.9.4

For a peek at what's currently possible, visit the documentation site, in particular the Usage section. For this initial release, it has feature parity with kubectx and kubens and that's about it, but there's lots of room for growth.

I also encourage you to install kubectx + kubens to navigate Kubernetes easily.