[X] I had searched in the feature and found no similar feature requirement.
Description
condation:
k8s use kata as a runtime which like a micro vm
streampark deployed on k8s and run a kubenetes application task
problems arising:
streampark can't connect to docker-daemon when run a kubenetes application task, because the following conf in k8s yaml does not take effect
volumeMounts:
i guess kata container and host use their own kernel due to this socket file can't mount to kata container
Why do I bring this up suggestion
docker may not be installed on k8s cluster because k8s use cotainerd + runc, now if we deploy streampark on k8s and we must install docker on all nodes in cluster, i don't want to do that , i want to install docker daemon on one node.
we don't worry about kubenetes can schedule streampark to any node if we install a docker daemon on one node which cluster node can connect to it
proposal:
install docker to support remote commutication
[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H tcp://192.168.10.100:2375 -H unix://var/run/docker.sock
Search before asking
Description
condation:
problems arising: streampark can't connect to docker-daemon when run a kubenetes application task, because the following conf in k8s yaml does not take effect volumeMounts:
i guess kata container and host use their own kernel due to this socket file can't mount to kata container
Why do I bring this up suggestion
docker may not be installed on k8s cluster because k8s use cotainerd + runc, now if we deploy streampark on k8s and we must install docker on all nodes in cluster, i don't want to do that , i want to install docker daemon on one node.
we don't worry about kubenetes can schedule streampark to any node if we install a docker daemon on one node which cluster node can connect to it
proposal:
install docker to support remote commutication [Service] ExecStart= ExecStart=/usr/bin/dockerd -H tcp://192.168.10.100:2375 -H unix://var/run/docker.sock
streampark conf docker: http-client: max-connections: 10000 connection-timeout-sec: 10000 response-timeout-sec: 12000 docker-host: "tcp://192.168.10.100:2375"
Usage Scenario
condation:
Related issues
No response
Are you willing to submit a PR?
Code of Conduct