Because it's fancy-kubectl !

• fzf
• kubectl
• kubectl tree
• kubectl neat - only for kexp to work
• jq

You can directly download the fubectl.source and save it in some directory.

Download:

curl -LO https://rawgit.com/kubermatic/fubectl/master/fubectl.source

then add to your .bashrc/.zshrc file:

[ -f <path-to>/fubectl.source ] && source <path-to>/fubectl.source

Alternatively you can install fubectl using the ZSH plugin manager of your choice.

Like g for git but 133% more effective!

Examples:

• k get nodes
• k get pods
• k version --short

Usage:

Examples:

• kw nodes
• kw pods
• kw nodes,pods,services

Get all pods

Usage:

Watch all pods in all namespaces every 2 seconds.

Usage:

Examples:

• kdes pod
• kdes service
• kdes nodes

Usage:

Examples:

• kdel pod
• kdel secret
• kdel pvc

Usage:

Examples:

• klog - Print the last 10 lines
• klog 100 - Print the last 100 lines
• klog 250 -f - Print the last 250 lines and follow the output, like tail -f
• klog 50 -p - Print the last 50 lines of the previous container

Usage:

Examples:

• kex bash - Start a bash in a container
• kex date - Print the date in a container

Usage:

Examples:

• kfor 8000 - Forwards port 8000 to a pod
• kfor 8000:80 Fowards local port 8000 to a pod's port 80

Usage:

Examples:

• // TODO

Usage:

Context list

Usage:

kcns - Set the current default namespace from list kcns kube-system - Set kube-system as default namespace immediately

Usage:

Opens localhost:8001/ui in your browser and runs kubectl proxy

Do you want to have the current kubecontext in your prompt?:

export PS1="\[$(kube_ctx_name)\] $PS1"

for the current namespace (this is currently slow, because it calls kubectl every time):

export PS1="\[$(kube_ctx_namespace)\] $PS1"

fubectl can be customized via following environment variables

• FUBECTL_WATCH_CMD - alterative watch command, e.g. viddy

If you encounter issues file an issue or talk to us on the #fubectl channel on the Kubermatic Slack.

Thanks for taking the time to join our community and start contributing!

Feedback and discussion are available on Kubermatic Slack.

• Please familiarize yourself with the Code of Conduct before contributing.
• See CONTRIBUTING.md for instructions on the developer certificate of origin that we require.

• We welcome pull requests. Feel free to dig through the issues and jump in.