Skip to content

@ahmetb ahmetb released this Jan 28, 2019 · 8 commits to master since this release

  • FIX: Show current context/ns color in interactive (fzf) mode. (#109)
  • TEST: Add integration tests for kubectx (#111, #113) and kubens (#105, #117)
Assets 2

@ahmetb ahmetb released this Nov 26, 2018 · 17 commits to master since this release

  • FEATURE: use XDG_CACHE_HOME to store data instead of $HOME/.kube if available
    (#93)
  • FEATURE: introduce KUBECTX_IGNORE_FZF variable to override interactive mode
    when fzf is detected (#82)
  • FIX: support Windows Subsystem for Linux (WSL) by detecting kubectx.exe in
    PATH when kubectl is not (#96)
  • FIX: zsh completion script glitch that printed only two contexts (#81)
  • IMPROVED: print errors when kubectl[.exe] is not detected in PATH (#92)
  • IMPROVED: better error handling when executed subcommands (like kubectl) fail
    (#95)
Assets 2

@ahmetb ahmetb released this Aug 24, 2018

  • FIX: fix crash when kubectx/kubens is installed --with-short-names and fzf(1)
    is in PATH, but calling the binaries with the wrong name. (#78)
Assets 2

@ahmetb ahmetb released this Aug 23, 2018 · 34 commits to master since this release

  • FEATURE: interactive search mode when kubectx and kubens are ran without any
    arguments and fzf(1) is detected in PATH. (#71, #74)
  • FIX: kubectx -d now doesn't ignore arguments after the first argument. (#75)
  • FIX: empty output bug when TERM=vt100 even though NO_COLOR is set. (#57, #73)
  • FIX: --help exits with code 0 now. (#69, #72)
Assets 2

@ahmetb ahmetb released this Aug 6, 2018 · 39 commits to master since this release

  • FEATURE: deleting multiple contexts at once with -d
  • FEATURE: customizing colors with KUBECTX_CURRENT_FGCOLOR and KUBECTX_CURRENT_BGCOLOR environment variables.
  • FEATURE: disabling colors in output with NO_COLOR environment variable or for non-tty output descriptors.
Assets 2

@ahmetb ahmetb released this Apr 9, 2018 · 62 commits to master since this release

  • SECURITY FIX: An issue that made it possible to do arbitrary code execution
    through kubens is fixed. A carefully crafted kubeconfig file that contains a
    context name with a slash (/) character and a crafted "namespace" field
    could cause any writable file to be replaced with arbitrary contents set in,
    the "namespace" field, leading to arbitrary code execution when used to
    replace contents of executable files.

    Since kubectx/kubens are not used in any production systems, this does not
    warrant a CVE. Please upgrade your kubens to use the patched version.

    This is fixed in #37 by @jvassev. See the issue for more information.

  • 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)

Assets 2

@ahmetb ahmetb released this Mar 30, 2018 · 70 commits to master since this release

  • Removed utils.bash: kubectx and kubens can now be used as standalone.
    • This is a breaking change for the installation scripts.
  • Added fish shell completion support.
Assets 2

@ahmetb ahmetb released this Nov 9, 2017 · 90 commits to master since this release

  • Breaking change: kubectx A=B now does a rename instead of
    creating an alias of the context.
Assets 2

@ahmetb ahmetb released this Nov 9, 2017 · 98 commits to master since this release

  • Fix: readlink issue on macOS.
Assets 2

@ahmetb ahmetb released this May 17, 2017 · 101 commits to master since this release

- Add kubens tool
- Add --with-short-names installation option
- Fix variables leaking to zsh session in completion
Assets 2
You can’t perform that action at this time.