Manage your Kubernetes client config file easily!
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Daniel Heitmann 9b18e6f999
Merge pull request #3 from dictvm/dependabot/npm_and_yarn/lodash-4.17.21
1 year ago
bin Move over to typescript 4 years ago
docs Update screenshots 4 years ago
src Assign item variable 3 years ago
.gitignore Move over to typescript 4 years ago
.prettierrc Add prettyrc 4 years ago
LICENSE Add License 4 years ago
README.md Update README title 3 years ago
jest.config.js Add first test 4 years ago
package.json Update dependencies 3 years ago
tsconfig.json Prevent building tests to dist 4 years ago
yarn.lock Merge pull request #3 from dictvm/dependabot/npm_and_yarn/lodash-4.17.21 1 year ago

README.md

Kubernetes Config File cleanup CLI tool

kube-cleaner-cli is a utility to keep your kubectl config-file in check.

Let's say you're using kops to manage Kubernetes clusters on AWS. You're not upgrading your clusters in-place but instead, you replace your clusters regularly. Maybe you've moved from minikube to Docker's Docker for Desktop. Or you're setting up lots of clusters for clients that you don't need anymore after the contract is done.

There are several valid reasons for your kubectl config to grow.

Of course you can manually clean them up or open $HOME/.kube/config in your text editor and edit YAML by hand, but you're not from the stone age, are you?

kube-cleaner makes it easy to keep track of your clusters, users and contexts and to delete them, as soon as you no longer need them.

screenshot showing first output of the applicaton

screenshot showing second output of the applicaton

Install

yarn global add kube-cleaner

or

npm install -g kube-cleaner

This assumes your yarn/npm-PATH is setup correctly. Please refer to their docs if kube-cleaner is not an available command after installation.