Kubernetes helper scripts

k9

#!/bin/bash
#
# A generic command that makes it easy to run k9s against a specific cluster 
# - without messing around with contexts (like kubectx does), eg:
#
# $ k9 prod-cluster get pods
#
# See the `kube` script alongside this one for more info (it's exactly the same except the final command is different)
#
set -ue -o pipefail

CLUSTER=$1
shift

CLUSTER_KUBECONFIG="$HOME/.kube/config.${CLUSTER}"

if ! [ -f $CLUSTER_KUBECONFIG ]; then
    echo "current-context: ${CLUSTER}" > $CLUSTER_KUBECONFIG
fi

export KUBECONFIG=${CLUSTER_KUBECONFIG}:$HOME/.kube/config

exec k9s $@

kube

#!/bin/bash
#
# A generic command that makes it easy to run kubectl commands against a specific cluster 
# - without messing around with contexts (like kubectx does), eg:
#
# $ kube prod-cluster get pods
#
# vs the complicated way, which makes it less expicit which cluster your commands will run against!
#
# $ kube set-context prod-cluster
# $ kubectl get pods
#
# It just works by looking for a ~/.kube/config.${1} kubernetes config, 
# then telling kubectl to "merge" that with its defalt config file
#
# It'll create a config file if one does not exist, assuming the context name is as given
# you can also just create your own and do things like override the default namespace etc
#
set -ue -o pipefail

CLUSTER=$1
shift

# Each cluster has its own config file
CLUSTER_KUBECONFIG="$HOME/.kube/config.${CLUSTER}"

if ! [ -f $CLUSTER_KUBECONFIG ]; then
    # All the config file does is override the current kubectl context
    # You can edit this file to add a default namespace too, if desired
    echo "current-context: ${CLUSTER}" > $CLUSTER_KUBECONFIG
fi

export KUBECONFIG=${CLUSTER_KUBECONFIG}:$HOME/.kube/config

exec kubectl $@