Support for other protocols

[BitTheByte]

Currently, the operator has a hardcoded TCP protocol

dask-kubernetes/dask_kubernetes/operator/controller/controller.py

Lines 155 to 159 in 92714da

	{
	"name": "DASK_SCHEDULER_ADDRESS",
	"value": f"tcp://{cluster_name}-scheduler.{namespace}.svc.cluster.local:8786",
	},
	]

[jacobtomlinson]

This is a great point, if the scheduler uses ws or ucx the controller wont be able to talk to it. Ideally, all communication would happen over the HTTP API but that isn't enabled by default right now.

Perhaps an annotation on the DaskCluster is the right way to handle setting the protocol for now?

[BitTheByte]

Looks like I didn't provide much information, this issue is about scheduler <=> worker communication, I'd like my cluster to communicate over ws rather than the hardcoded tcp protocol since you also mentioned it, the operator would also need this information to be able to contact the scheduler, I'm thinking of something like

apiVersion: kubernetes.dask.org/v1
kind: DaskCluster
metadata:
  name: dask-f3a0c12f
  namespace: default
spec:
 protocol: "ws"
 scheduler:
  ....

[jacobtomlinson]

Ah yep I see what you mean. I agree that extending the CRD to include a protocol field makes sense. We will need to handle #753 in order to do this.