This is a kubectl plugin that is built to simplify creating resources in a team's namespace.
Use of this plugin requires no previous knowledge of Kubernetes manifests and namespaces. A team member can be sure that the resource is created with the correct labels, using the correct requirements for the Kubernetes API and that it ends up in the right place in Kubernetes. The plugin makes use of the ID token in the kubeconfig to figure out which team the user belong to.
Currently supported resource types:
- Secrets
Download the kubectl-tbac binary from releases Place binary in directory for example kubectl-tbac
You can add it to your $PATH in ~/.bash_profile or ~/.profile
export KUBECTL_TBAC="$HOME/kubectl-tbac"
PATH=$PATH:$KUBECTL_TBAC
export PATH
reload: source ~/.bash_profile
Add system variable KUBECTL_TBAC with path to kubectl-tbac directory containing binary Add to Path %KUBECTL_TBAC%
Once in your $PATH you can start using kubectl tbac.
git clone [email protected]:Bisnode/kubectl-tbac.git
cd kubectl-tbac
$GO111MODULE=auto go build
Some examples of how to manage kubernetes secrets using kubectl-tbac.
Create secret
kubectl tbac create secret my-secret --data "USERNAME=foo" --data "PASSWORD=bar"
Update secret
kubectl tbac patch secret my-secret --data "URL=github.com" --data "USERNAME=bar" --remove-data "PASSWORD"
List secrets
kubectl tbac get secrets
Describe one secret
kubectl tbac get secret my-secret
Delete secret
kubectl tbac delete secret my-secret
Show version of the plugin
kubectl tbac version
All commands accepts a --[h]elp flag for more information and examples.
Some windows users have reported that kubectl tbac returns a cryptic error message about "not supported on windows". In that case you may call the program directly (and not as a kubectl plugin) by issuing kubectl-tbac (note the "-" between kubectl and tbac).
Example:
kubectl-tbac get secrets