smartive / kuby Goto Github PK

;-)

sops does that :)

it would be nice to dryrun (and therefore output) create secret, so it could be copy pasted

The k8s namespace create command does create a namespace and asks the user many things.

A ci mode (which is already globally defined in yargs) support would mean:

• ci mode implies no-interaction
• ci mode does create the namespace with the given name
• ci mode does execute k8s namespace kube-config <namespace> <account> (like it does now) but also with ci mode.
• additional --role argument that allows a role.yml file to be passed for the role binding in the namespace

ci mode in k8s namespace kube-config <namespace> <account> would mean:

• create the specific kube-config for the namespace and the account and perform a login like k8s kube-config
• don't output the kube-config

Some features of the k8s tool are not available in certain kubectl versions. (e.g. k8s namespace kube-config)

It should be prevented to execute commands that are not available for the given kubectl version.

Example

k8s namespace kube-config should return a kube config for a given user (most likely a service account)
in a given namespace. The problem with the context in the config is that below kubectl 1.xx the
certificate data is "BUFFER" encoded instead of base64 encoded. -> This leads to broken configurations.

There is a library (@kubernetes-clients/javascript) that would remove the need of kubectl locally.
Kubectl version managing could still be a part of kuby (like nvm for node) but internally kubectl is not needed for interacting with kubernetes.