Releases: jinnovation/kele.el
0.6.0: Permissions, kind-specific keybindings, list improvements
Note
This release bumps the minimum required version of Emacs to 29.
This release fleshes out the resource listing functionality. Some highlights:
- In addition to opening a resource from the list view (
RET), you can now also delete/kill the resource at point withk; - The list view now shows the owner resource(s) for every list item; hitting
RETwith your cursor over the owner cell will instead open the owning resource; - The list view now supports listing across all namespaces.
This release also introduces the notion of kind-specific keybindings. Some resources have special "actions" associated with them, e.g. "restarting" Deployments or getting logs from Pods. kele-resource now has a dedicated column for these keybindings that, when defined, are dynamically filled in based on the selected resource kind. For now, there is only one resource-specific keybinding—R to restart a Deployment. Try s-k deployments to check it out.
Lastly, individual bindings within kele-resource are disabled based on your permissions for the given context/cluster. In other words, if you don't have permission to list Pods within the selected cluster, Kele will disable the l keybinding with a helpful message.
Enjoy!
v0.5.0: Menu bar + doom-modeline integration!
This release integrates Kele with the Emacs menu bar. With this initial integration, you can switch Kubernetes contexts and default namespaces from within the menu bar. Kele presents your available contexts and namespaces as dynamic sub-menus, freeing you from the need to remember exact names and typing them in by hand (similar to kubectx and kubens on the terminal).
With this release, Kele is now also integrated with doom-modeline. By adding the k8s segment to your doom-modeline configuration, you'll see current context and namespace information directly on the modeline. The menu bar is also accessible here as well, for the (menu-bar-mode -1) crowd.
v0.4.2
Fixed
- Fixed a bug where
kele-modeerrors out when the kubeconfig file does not
exist yet - Fixed a bug where
curlerrors are not properly caught, resulting in attempts
to query the kubectl proxy server before it is ready
Changed
- Bumped dependency
plzfrom0.3to0.7.3
0.4.1
Fixed
- Fixed an issue where Kele can exhaust the number of file descriptors available for Emacs to use.
- Fixed an issue where command families that require proxy servers, e.g.
kele-resource, result in false-positive
timeout errors when starting up the proxy server.
Changed
- Discovery cache polling is now timer-based instead of "dynamic," i.e. in response to filesystem changes.
0.4.0
Lots of fun stuff in this release.
Most importantly, Kele 0.4.0 introduces kele-list (s-k <resource type> l)
and -- with it -- the ability to list all resources of a given type in tabulated
form. Before, you could only fetch single resources. Now, with kele-list, you
can create ad-hoc "overviews" of specific resource types within a given context
and namespace; hitting Enter on any entry in this list brings up the resource's
full manifest.
Kele 0.4.0 also introduces the kele-proxy command palette (s-k p) for
starting/stopping proxy servers for contexts. It also fleshes out the Kubeconfig
management command palette (s-k c).
For more details, see: How-Tos > Usage.
Added
- Added a
kele-proxycommand prefix for managing proxy servers - Added a keybinding to
kele-contextto enable/disable the proxy server for
the current context - Added a keybinding to
kele-contextfor deleting a context - Added a keybinding to open
kele-kubeconfig-pathin a buffer - Added a keybinding to
kele-resourceto support listing out all resources of
a given type (kele-list)
Fixed
kele-contextandkele-resourcenow wait on kubeconfig sync completion to
finish if one is currently in progress- Fixed a bug where force-enabling or force-disabling
kele-mode(via either
(kele-mode 1)or(kele-mode -1)) whenkele-modeis already active or
inactive (respectively) resulted in errors - Fixed an issue where attempting to invoke
s-k <resource name> gsometimes
results in the following error:transient-setup: Suffix transient:kele-resource::command is not defined or autoloaded as a command
Changed
- Renamed
kele-contexttokele-config - Increased the default value of
kele-proxy-ttlfrom60to180 - Binding for
kele-getinkele-get-modechanged fromUtog
0.3.0
This release focuses on providing Kele's command palette and user interface with
a scalable foundation for future growth. As Kele's spread of user-facing
commands grows, it becomes less and less reasonable to expect users to M-x
everything.
To that end, this release adds the following:
- A Kele command keymap that will allow keybinding-based access to all
Kele-based functionality (see How-Tos > Customization and How-Tos > Usage
for more details) - A spread of three Transient-based "prefix" commands --
kele-context,
kele-resource, andkele-dispatch-- for nested command discovery and
ad-hoc configuration, e.g. overriding the context and namespace to use for
resource fetching. Again, see How-Tos > Usage for more details.
I'm optimistic that these two additions make Kele's user interface much more
pleasant and nimble, while also giving it ample room to grow in complexity and
scope in the coming releases.
Added
kele-getresource name input now supports completion! 🔥kele-getbuffers now have keybindings for quitting and killing the resource
display buffer- You can now press
Uinkele-getbuffers to re-fetch and refresh the
current resource kele-getbuffers' front matter now outlines the available keybindings- Added a
kele-dispatchcommand for when you forget the specific keybinding of
what you're trying to accomplish - Added a
kele-contextcommand prefix for context-related actions - Added a
kele-resourcescommand prefix for acting on specific resource kinds,
e.g.getting, with support for selecting the context, namespace, and the
group-version to use (in cases of ambiguity)
Changed
0.2.1
This release focuses on refining the kele-get experience -- usability
improvements and general bugfixes.
Added
kele-getbuffers now have a dedicated minor mode,kele-get-mode.kele-getbuffers now print a header detailing, for the resource under
display: the context it was fetched from; and the time of retrieval- Added a custom variable
kele-filtered-fieldswith which you can routinely
filter out resource fields from display inkele-get
Fixed
- Fixed an issue where
kele-getresults buffer incorrectly prints namespace
for un-namespaced resources asnil - Fixed an issue where
kele-getrefused to display the retrieved resource, if
a buffer corresponding to that resource already exists
Changed
kele-getcompletion for the resource type now only returns resources that
support thegetverb
v0.2.0: Introducing `kele-get`
This release introduces kele-get -- kubectl get, the Emacs way
🚀. With kele-get you can interactively specify the kind and name of the
resource that you'd like to get and display its manifest in a separate
buffer. What's more, it supports custom resources right out the gate -- a
long-standing functionality gap in kubernetes-el.
See How-Tos > Usage > Working with
Resources for details and a demo
GIF. It's very much an MVP so there are some rough edges. Please open an issue
for any peculiar behavior that you notice.
Added
- Implemented
kele-getfor interactively getting and displaying a given
resource - Context annotations now display whether a proxy server is currently active for
the given context - Implemented interactive functions for per-context proxy server management:
kele-proxy-start,kele-proxy-stop, andkele-proxy-toggle
Fixed
- Fixed an issue where disabling
kele-moderesulted in an error reporting
unbound slotfilewatch-idonkele--discovery-cache - Fixed an issue where cluster servers with ports,
e.g.https://127.0.0.1:51134, were not recognized properly - Fixed an issue where namespace completion candidates failed to populate on
initial fetch of said namespaces from the Kubernetes API
Changed
- Buffer for contexts' proxy processes are now hidden
- Default value for
kele-cache-diris now~/.kube/cache; before it was
relative to the value ofkele-kubeconfig-path(and unreliably so)
0.1.1
Added
- Kubeconfig file watching is now asynchronous and therefore non-blocking!
- Kubeconfig file watching now prints a [progress report] denoting when changes
were detected (and thus reading has begun asynchronously) and when reading has
completed
Fixed
- Fixed an issue where proxies were being created for the current context,
regardless of which context it was actually requested for - Fixed an issue in
kele-namespace-switch-for-contextwhere the selection
candidates were pulled for the current context rather than the argument
context - Fixed an issue where attempting to pull completion candidates via queries to
the proxy API server resulted in an error, as well as multiple proxy server
processes being inadvertently spun up for the same context - Fixed an issue where custom kubeconfig path is not respected by
kubectl
invocations
Inaugural release 🎉
Kele is born!
This initial release of Kele has a very simple goal: "kubectx and
kubens, but make it Emacs." Its feature set is limited but lays the
foundation -- both in terms of implementation and "design philosophy" -- for
future enhancements.
Added
- Added ability to switch and rename contexts, with completion and caching
- Added ability to switch namespaces for any given context
Full Changelog: https://github.com/jinnovation/kele.el/commits/v0.1.0


