Closed AlanGreene closed 3 years ago
https://github.com/mumoshu/config-registry
might just stick to existing approach with KUBECONFIG
environment variable and custom aliases (e.g. idsprod
)
https://github.com/corneliusweig/rakkess
looks useful, maybe cook up something similar but simpler / more tailored to my own needs
what are the benefits over kubectl auth can-i --list
or similar?
ln -s /usr/local/Cellar/kubectx/0.6.3/etc/bash_completion.d/kubectx ~/.bash_completion/kubectx
ln -s /usr/local/Cellar/kubectx/0.6.3/etc/bash_completion.d/kubens ~/.bash_completion/kubens
kube-ps1 ?bash prompt
KUBE_PS1_ENABLED=off
kube_prompt() { if [[ "${KUBE_PS1_ENABLED}" = "on" ]]; then echo "${bold}${orange}
kubectl config current-context
${white}:${cyan}kubectl config view -o'jsonpath={..namespace}'
${reset}" fi; }kubeon() { KUBE_PS1_ENABLED=on }
kubeoff() { KUBE_PS1_ENABLED=off }
aliases (clean this up, combine alias + completion)
/etc/shells
to add/usr/local/bin/bash
chsh -s /usr/local/bin/bash
echo $BASH_VERSION
to verify~/.bash_completion/
to~/.bash_completion.d/
as.bash_completion
is expected to be a file (also update reference in~/.bash_profile
)