We're moving to an environment where our drupal instances will live inside docker containers managed by kubernetes.

Currently I've got scripts for things like checking module security status across large numbers of drupal sites. Basically I maintain a file full of aliases, and I iterate over those. It works well enough.

With the move to kubernetes, what I'd like to happen is that my aliases would somehow specify that the way to call the remote instance is via a kubectl command that effectively invokes drush in the remote container. It looks a lot like an alternative to ssh as the transport.

  1. Is something like this possible?
  2. OK, so I've got the source code, and anything is presumably possible, but what might a sensible approach look like? What should I look at to get my head around this?
  • did you come up with any solution? Apr 16, 2020 at 18:50

1 Answer 1


It seems that you currently can't change the transport / replace SSH. However, most of the work can be fixed be writing wrapper scripts. Read https://github.com/drush-ops/drush/issues/2367

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.