unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 59797@debbugs.gnu.org
Subject: bug#59797: 30.0.50; [wishlist] Using namespaces in Tramp's kubernetes integration
Date: Tue, 06 Dec 2022 16:56:30 +0300	[thread overview]
Message-ID: <m21qpcmy9d.fsf@fastmail.fm> (raw)
In-Reply-To: <874ju96e2g.fsf@gmx.de> (Michael Albinus's message of "Mon, 05 Dec 2022 16:54:47 +0100")

Hi Michael,

On 05/12/2022 16:54 +0100, Michael Albinus wrote:

>> My motivation behind adding limited k8s support to Tramp was to be able
>> to login into pod.  A service is a more high-level abstraction, you
>> cannot log into service, as there're some particular pods behind it.
>> From my limited knowledge and experience of k8s, listing pods in the
>> current namespace is ok.  We could add more scenarios when the need
>> arises.
>
> I don't speak about services in general. I speak about pods.
>
> Imagine, you have "pod1" in your current context, and "pod2" in another
> namespace, call it "another-namespace".
>
> "kubectl get pods" shows you "pod1". "kubectl get pods --namespace
> another-namespace" shows you "pod2".
>
> "kubectl exec pod1 -it -- /bin/sh" access pod1 in your current
> context. This is what we use when we access via remote file name syntax
> "/kubernetes:pod1:".
>
> pod2 is not accessible in your current context. But you could apply
> "kubectl exec pod2 -it --namespace another-namespace -- /bin/sh". This
> is what I mean with remote-file name syntax "/kubernetes:pod1.another-namespace:".
>
> Is this possible?

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

Filipp





  reply	other threads:[~2022-12-06 13:56 UTC|newest]

Thread overview: 15+ 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 [this message]
2022-12-06 15:13       ` Michael Albinus
2023-06-23 19:47         ` Michael Albinus
2023-07-02  8:37           ` Michael Albinus
     [not found]           ` <m1cyn4cq38.fsf@eshelyaron.com>
2024-07-23 12:29             ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-23 12:59               ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-23 14:13                 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-24 16:48                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-24 17:30                     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25  8:20                       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25 10:48                         ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25 11:42                           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m21qpcmy9d.fsf@fastmail.fm \
    --to=fgunbin@fastmail.fm \
    --cc=59797@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).