kubectl attach via proxy pods

[mhuysamen]

It seems that Admiralty's proxy pods don't support attaching to scheduled candidate pods.

I'm trying to use Admiralty in conjunction with Submariner to bind several k8s clusters, and have AWX spawn automation jobs across them. It seems that AWX, once it launches a worker container, attaches to the container to send it instructions via stdin, and reads output via stdout.

If this isn't currently supported, could this be added, that once the POD is Running, the Proxy pod attaches to the Candidate for stdin/stdout. This could be activated conditionally with an extra annotation, like multicluster.admiralty.io/attach=true, since this functionality would only be required in specific workloads/conditions.

[adrienjt]

We support exec (and logs). So adding attach shouldn't be hard. This was an oversight.

[adrienjt]

Not so fast though. Virtual-Kubelet only supports exec and logs, so we'll have to fork or upstream this piece: https://github.com/virtual-kubelet/virtual-kubelet/blob/master/node/api/server.go

[adrienjt]

Attach is now supported by VK: virtual-kubelet/virtual-kubelet#1090