Following up: according to the linked doc, it looks like TLS/SSL can be implemented via keyword arguments on the Dask Client. We pass all extra keyword arguments to

DaskExecutor(**more_kwargs)

to the client, so this might be an effective workaround. https://distributed.dask.org/en/latest/tls.html Aside from that, you raise a good point, and we'd love to implement more robust support for this in the future. Thank you for raising this point!