From: Michael Albinus <michael.albinus@gmx.de>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: 59797@debbugs.gnu.org, Aaron Gonzales <aarongonzales1@gmail.com>,
Warren Lynn <wrn.lynn@gmail.com>
Subject: bug#59797: 30.0.50; [wishlist] Using namespaces in Tramp's kubernetes integration
Date: Fri, 23 Jun 2023 21:47:37 +0200 [thread overview]
Message-ID: <87y1kaq7ty.fsf@gmx.de> (raw)
In-Reply-To: <87bkogr2e5.fsf@gmx.de> (Michael Albinus's message of "Tue, 06 Dec 2022 16:13:38 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi,
>> Maybe, and there's "get pods -A" which lists all pods. This will be
>> limited to current "context" in k8s meaning (covering all namespaces in
>> it). I could look into this in detail in few weeks, if you'd like me
>> to. It's quite a busy time at work now :-)
>
> Take your time. Emacs 29.1 is on its release path, so any feature change
> won't be pushed there. We could plan it for Emacs 29.2.
Finally, I've taken the stab and implemented something along these
lines. It is a little bit different from earlier proposals.
- You can now specify a container in the host name, dotted notation.
"/kubernetes:container.pod:" accesses the given container. If it is
not specified, as in "/kubernetes:pod:", the first container is taken.
- You can now specify different context and namespace. Change the new
user options tramp-kubernetes-context or tramp-kubernetes-namespace
for this effect.
Everything pushed to the Emacs and Tramp master repositories. The target
is now Tramp 2.7 / Emacs 30. Comments welcome :-)
Best regards, Michael.
next prev parent reply other threads:[~2023-06-23 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 9:20 bug#59797: 30.0.50; [wishlist] Using namespaces in Tramp's kubernetes integration Michael Albinus
2022-12-05 14:05 ` Filipp Gunbin
2022-12-05 15:54 ` Michael Albinus
2022-12-06 13:56 ` Filipp Gunbin
2022-12-06 15:13 ` Michael Albinus
2023-06-23 19:47 ` Michael Albinus [this message]
2023-07-02 8:37 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1kaq7ty.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=59797@debbugs.gnu.org \
--cc=aarongonzales1@gmail.com \
--cc=fgunbin@fastmail.fm \
--cc=wrn.lynn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.