TRAMP + Emacs 30

[johnhamelink]

Hi there,

I'm running Emacs from master branch. Emacs 29 comes with support for Kubernetes, Podman and Docker as TRAMP "inline methods" (see here).

• To start, we can use tramp-kubernetes-program as the default path for kubectl for Emacs 29+
• We should be able to transition away from implementing our own kubectl TRAMP method, and towards using the official kubernetes method instead.
  • Context & namespace should be defined with tramp-kubernetes-context and tramp-kubernetes-namespace (https://github.com/emacs-mirror/emacs/blob/master/etc/NEWS#L439).
  • Container an pod should be defined in the path: https://github.com/emacs-mirror/emacs/blob/master/lisp/net/tramp-container.el#L47

[abrochard]

Hi @johnhamelink , Thank you for sharing this! I was not aware of these changes at all. This is actually a trickier change than first anticipated because we also have to keep things working for people running versions anterior to 29:

• we can probably do some smart logic and try to default/fallback to tramp-kubernetes-program if defined
• similarly we should keep the old TRAMP method if tramp-kubernetes-method isn't defined
• I think that <kubectl> config use/set-context <context> is global? as in it will change the context for the whole machine, which is something that kubel doesn't do at all today and could have un-intended consequences

I'm also still on 28 and not sure when I will upgrade/find time to work on this.

[johnhamelink]

We can probably do some smart logic and try to default/fallback to tramp-kubernetes-program if defined similarly we should keep the old TRAMP method if tramp-kubernetes-method isn't defined

Sounds good!

I think that config use/set-context is global?

That's right. I wonder if instead we could supply environment variables to the underlying kubectl process?

Another issue is that according to the docs, "The first container in a pod is used", which is rather limiting for Kubel's use-case. Similar tools like k9s allow you to select the pod - often the first pod is actually istio-proxy or a similar "sidecar" pod which is less interesting.

[linktohack]

This works for me

  (with-eval-after-load 'tramp
    (require 'tramp-container)
    (when-let* ((method (thread-last tramp-methods
                     (seq-find #'(lambda (it) (pcase it (`("kubernetes" . ,_) t))))))
        (updated (pcase method (`(,_ . ,rest) `("kubectl" . ,rest)))))
      (add-to-list 'tramp-methods updated)))

It inserts kubectl method with the same config of kubernetes method defined in tramp-container

Hope it helps.

[johnhamelink]

FYI it's now possible to define a container ID along with a pod in Emacs master: https://github.com/emacs-mirror/emacs/blob/master/lisp/net/tramp-container.el#L47

It seems that the namespace and context can be defined now too: https://github.com/emacs-mirror/emacs/blob/master/etc/NEWS#L439