konfig
konfig copied to clipboard
Change semantics of "split"
Currently, "split" is an alias for "export". However, the connotation of split is more that the two outcomes have disjoint contexts instead of one being a subset of the other.
Maybe split should really do a split, so that the split out context is no longer contained in the input kubeconfig file.
TODO: work out how this should behave with multiple input kubeconfigs when KUBECONFIG=cfg1:cfg2...
.