Support running Dask with Istio / Envoy proxy
See original GitHub issueIn order to run Dask with Envoy enabled, each worker needs to have service created and expose it through contact-address
, I was wondering if we can add creation of a service to the worker through a worker-template, e.g. not assume its a single pod definition inside a template, but consider service definition as well if defined ?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Debugging Envoy and Istiod
Istio provides two very valuable commands to help diagnose traffic management configuration problems, the proxy-status and proxy-config commands.
Read more >Running Kubeflow inside Kind with GPU support
This week I've been playing around with Kubeflow as part of a larger effort to make it simpler to use Dask and RAPIDS...
Read more >Recently Active 'istio"' Questions - Page 9 - Stack Overflow
I have a service running in namespace istio-system , I want to connect it with pod in different namespace say default . My...
Read more >Tag: Google Kubernetes Engine - GCP Weekly
Traffic Director: TLS routing using Envoy gateway proxy on GKE - We share a sample ... help customer shift left security for kubernetes...
Read more >Intel® Developer Catalog
Istio * extends Kubernetes* to establish a programmable, application-aware network using the Envoy* service proxy. Working with Kubernetes and traditional ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This would be great if one would want to use dask kubernetes with kubeflow (Uses istio all over the place).
I’m to close this issue out now. We have a workaround for the classic
KubeCluster
with https://github.com/dask/dask-kubernetes/issues/197#issuecomment-1048593317 and do not intend to ever add true support there.The operator is the path forwards and are tracking Istio support there in #482 where we have an implementation plan.