unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Aaron Gonzales <aarongonzales1@gmail.com>,  emacs-devel@gnu.org
Subject: Re: Feature to allow selection of container when connecting to kubernetes pod
Date: Tue, 03 Jan 2023 04:14:52 +0300	[thread overview]
Message-ID: <m28rikto4z.fsf@fastmail.fm> (raw)
In-Reply-To: <87h6xbg9dw.fsf@gmx.de> (Michael Albinus's message of "Sat, 31 Dec 2022 11:22:51 +0100")

Hi Michael and Aaron,

On 31/12/2022 11:22 +0100, Michael Albinus wrote:

>> These new changes allow the user to select a container when connecting
>> to a kubernetes pod. This is essential for kubernetes Tramp
>> functionality since the first container may not always be the desired
>> pod. Many pods contain multiple side-car containers besides the main
>> application container.
>
> Sounds useful to me.

To me too, however I think we should agree on a filename syntax.  I
don't have vast experience with Kubernetes, and thus chose the simplest
thing to do first - just accessing pods by name.  When we add other
specifiers, we should add them in a consistent way.  I haven't looked at
the docs in detail yet, and am mostly offline while it's holiday time
here, but will be able to do that in January.  Of course, if Michael
arrives at some opinion in the meantime, I fully trust his decision.

Thanks,
Filipp



  reply	other threads:[~2023-01-03  1:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 13:53 Feature to allow selection of container when connecting to kubernetes pod Aaron Gonzales
2022-12-31 10:22 ` Michael Albinus
2023-01-03  1:14   ` Filipp Gunbin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-30 20:58 Aaron Gonzales

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=m28rikto4z.fsf@fastmail.fm \
    --to=fgunbin@fastmail.fm \
    --cc=aarongonzales1@gmail.com \
    --cc=emacs-devel@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).