kubeconfig-merge: Painless and faultless way to merge kubeconfig files

---

Why is it developed?

If you are someone who works with a significant number of Kubernetes clusters, dealing with kubecontext in a manual way can be boring and also result in problems. In addition to that, I am currently working with more than 20 customers, which results in an average of five clusters per customer.

Install

Install on Linux

The following instruction list covers all of the Linux distributions (Ubuntu, Debian, Redhat, CentOS, RHEL, etc.) that provide sh as an executable:

(
    set -x
    EXEC_PATH="/usr/local/bin/kubeconfig-merge"
    cd "$(mktemp -d)" &&
        OS="$(uname | tr '[:upper:]' '[:lower:]')" &&
        ARCH="$(uname -m | sed -e 's/x86_64/amd64/' -e 's/\(arm\)\(64\)\?.*/\1\2/' -e 's/aarch64$/arm64/')" &&
        FILENAME="kubeconfig-merge_${OS}_${ARCH}" &&
        curl -fsSLO "https://github.com/btungut/kubeconfig-merge/releases/latest/download/${FILENAME}" &&
        sudo rm -rf "$EXEC_PATH" && sudo cp "${FILENAME}" "$EXEC_PATH" && sudo chmod +x "$EXEC_PATH"
)

Install on Windows

TBD

Arguments

Argument	Description	Default
file	The additional kubeconfig file	Required
kubeconfig	The kubeconfig file which to be append into	KUBECONFIG env variable, or ~/.kube/config
name	Context, cluster and user name of new entries	File name of --file

Examples

---

./kubeconfig-merge --file valid-default-cluster.yaml

---

./kubeconfig-merge --file valid-default-cluster.yaml --name foo

Contributors

Ohki Nozomu