Vedran Lerenc

There is another angle/dimension: the `kubectl` version and whether or not it fits the shoot cluster Kubernetes version. The skew policy https://kubernetes.io/docs/setup/release/version-skew-policy/#kubectl means we would have to pick the right...

Isn't here the main problem, how to get to the cluster operation logs in the first place @grolu , cc @rfranzke?

I think, this is a misunderstanding. This is a very old story or rather epic and it is most likely nothing that can be "just implemented". It will need planning...

Hmm... @grolu we have the Dashboard covered in AvS, so what is this issue about? As for #447 these would be monitoring changes, but we wouldn't fail the AvS probe,...

@marwinski Sounds like a reasonable behaviour, i.e. auto-start `sshd` only in the case, that the node cannot join the cluster - for a limited time. The danger should be limited,...

Why would we consider it "unsupported"? Key stakeholders of ours that are using for instance `nfsd` wouldn't understand/accept that. Then they wouldn't use it and we would be back at...

> The best UX would be to have a top-level plugin (k orphan or k diag) which can call out to provider-specific implementations. @timebertt Yes, from experience with /diag in...

> Continuing the session by default is dangerous, so we would need some command to continue the last session on demand, meaning targeting the last cluster again. Then operators can...

Use case B is (maybe) harder and generally another problem. It's also bugging me and my workflows. Generally, I would very much like to have a solution that provides me...

@timebertt Hmm... isn't a general `clone` difficult? Let's say, your current `kubeconfig` is one in a local folder backing a `git` repo or whatever. Where would you physically clone the...