GNU-devel ELPA - kubed

Kubed commands run kubectl in the buffer from which you invoke them, so settings that affect kubectl, from environment variables such as KUBECONFIG to running on a whole other host via Tramp, can differ from one buffer to the next. Kubed now treats each distinct combination of these settings as an “execution environment”, and keeps its state separate for each one. This lets you work in parallel with clusters reached through different KUBECONFIG files (for example as set per-directory by https://github.com/purcell/envrc). The new “Execution Environments” section in the Kubed manual provides additional details.

See feature request at https://lists.sr.ht/~eshel/kubed-devel/%3C80aeac01-e21a-4823-a5ae-abe7b7a7a6f7@app.fastmail.com%3E

This version fixes a regression introduced in version 0.6.0, which caused an error when starting a shell or opening Dired inside a pod.

See bug report at https://lists.sr.ht/~eshel/kubed-devel/%3C87zf36vqaa.fsf@gmail.com%3E

When you invoke Kubed commands in a buffer whose default-directory points to a directory on a remote host (such as /ssh:user@example.com:/some/remote/dir/), Kubed runs kubectl on the remote host, so you can interact with clusters that are configured in the remote kubeconfig and accessible from the remote host.

Note that this is a rather extensive change, please tell us about issues/regressions if you see any!

You can configure different kubed-kubectl-program values for different hosts on which you run kubectl via Kubed commands, by giving the variable a connection-local value for certain hosts. For example:

(connection-local-set-profile-variables
 'my-kubed-profile-for-somehost
 '((kubed-kubectl-program . "/home/user/my-kubectl")))

(connection-local-set-profiles
 '(:application kubed :machine "somehost.com")
 'my-kubed-profile-for-somehost)

This user option generalizes and supersedes the existing user option kubed-default-context-and-namespace, which is considered obsolete but is still available. The new user option lets you set different defaults depending on the host on which Kubed is running kubectl.

This was already a recommended binding for this command, which opens the “root” Kubed transient menu.

The new user option kubed-logs-follow controls whether Kubed follows new log entries by default when showing Kubernetes logs. It defaults to t.

Kubed commands that show logs for Kubernetes resources now fetch only the most recent 128 log lines by default, to avoid flooding the logs buffer with the full history of long-running workloads. You can customize this limit with the new user option kubed-logs-tail-lines; set it to 0 to fetch all available log lines.

… …