kubectx VS ksniff

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.

so probably the right way is to use some tool like that (ksniff) or setup a sidecar container. But I am still curious to why I get the above error.

I've used https://github.com/eldadru/ksniff with success. Recently on this sub Kubeshark was also mentioned.

Link to GitHub Repository

There also is https://github.com/eldadru/ksniff which starts wireshart GUI

I have used Ksniff as a kubectl plugin that act as a "Wireshark tool" for containers https://github.com/eldadru/ksniff

I've found ksniff useful for monitoring Kubernetes traffic with wireshark: https://github.com/eldadru/ksniff

KSniff https://github.com/eldadru/ksniff lets you do full packet capture.

ksniff - known as sniff is a tool for debugging and capturing networking data. It's able to attach to a pod and using tcpdump to forward networking data to your local Wireshark. This tool also works pretty well with tshark - the command-line version of Wireshark.

Install ksniff - https://github.com/eldadru/ksniff#installation