v0.5.0 (2018-04-09)
- SECURITY FIX: A context name that contains '/' in the name could arbitrarily
overwrite any on the filesystem through a crafted context name when it is
used with kubectx.
This is fixed in #37 by @jvassev. kubectx now handles context names with '/'.
- FEATURE: Renaming context will now overwrite if the specified name already
exists, through deleting the existing context entry in kubeconfig. (#25)
- FEATURE: Deleting context entries in kubeconfig with "kubectx -d NAME" ('.'
for current). This only deletes the context entry and does not touch 'users'
and 'clusters' keys in kubeconfig (and therefore might leak those entries).
Use this only if you do not care about the extra values in your kubeconfig.
(#23, #38)