Re: master 55eabe96c9: ; Improve manual for Tramp kubernetes method

[Filipp Gunbin <fgunbin@fastmail.fm>]

Hi Michael,

On 25/10/2022 19:48 +0200, Michael Albinus wrote:

> Filipp Gunbin <fgunbin@fastmail.fm> writes:
>
>> Something messed up in the mailing list (or in my Gnus config :-), I see
>> only some messages in this thread from today.
>
> I recommend to read such MLs via news.gmane.io (as I do). No problems
> today.

After "make bootstrap", I now see the messages, don't know what was the
cause.

>> Anyway: I'll test the new patch a bit later, now just wanted to return
>> to current-context thing.  I'm still sure that we need to cache full
>> config, because a user may change context as easily as a namespace.  In
>> fact, a context _is_ a namespace, in a sense, just higher-level
>> namespace.
>
> My proposal is to check all fields of current-context. Like this:
>
> # kubectl config view -o jsonpath='{.contexts[?(@.name == "docker-desktop")]}'
> {"context":{"cluster":"docker-desktop","user":"docker-desktop"},"name":"docker-desktop"}
>
> This includes the name of the current context ("docker-desktop"), and if
> the user switches to another context, or changes an attribute of the
> current context, it will differ.
>
>> Also, context refers to "cluster" by name, and cluster config also may
>> change, etc.
>
> Yes, but we cannot check everything. Compare it to an ssh connection,
> which uses a Host entry in .ssh/config. If a user changes the Hostname
> part of that Host entry, it isn't detected either by Tramp. The user is
> responsible for this kind of changes, and the consequences.
> 
> And remember, this discussion started because you were concerned about a
> changed namespace, nothing else.

I think I now agree with you, let's use this approach for now.

I'll give it more testing and will write back.

Thanks,
Filipp