kubectx VS kube-ps1

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.

I meant bash/zsh PS1 prompt. Not PowerShell :) Check this out https://github.com/jonmosco/kube-ps1

I use kube-ps1 to put cluster info in my shell prompt.

kube-ps1: Kubernetes prompt for bash and zsh

kube-ps1 🥇 ⌛ - ZSH plugin for kubectl that adds current context and namespace.

This is the PS1 I've been using for a long time. Note it needs the git-prompt.sh script (usually comes with the bash-completion) package, and the kube-ps1 script: https://github.com/jonmosco/kube-ps1

It will show you the current kubernetes profile and namespace, user@host, current directory and git branch if you're in a git repo.