2 answers

I'm not fully sure what Geoff had in mind as a workaround here. He's on leave until next week so I can't ask him until then. As far as I know this isn't possible as Swarm commands aren't available at the moment. But, I'll check with Geoff when he's back.

I don't have an ETA on when we may have a similar guide on Swarm in our own documentation. However, those links should suffice for you by translating the appropriate commands into commands in your deploy step script.

Thanks,

Phil

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

For the same reason why kubectl tries not to use it..and every platform provides a SSL/TLS API.

Being able to physically log in to a server is a different security envelope with different considerations. For example, once you are on the server - you can attempt Spectre/Meltdown. You cannot do that with remotely issued docker commands over TLS.

In general, we would strongly request for a transport level security over being able to SSH.

IMHO both k8s and swarm have it - it's just a question of how to set it up with your infrastructure.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.