Add IngressSpec besides ServiceSpec to Scheduler about dask-kubernetes HOT 2 CLOSED

Tried that out, works great! Thanks a lot :)

from dask-kubernetes.

Thanks for raising this @jonded94, glad you're enjoying Dask.

I'm pretty cautious about adding new nested resources to the spec because it could easily snowball as people request more and more things to be added. I would prefer people to create additional resources independently, but I'm very open to improving tooling to make that easier.

We set owner references on all the child resources we create so that when the DaskCluster resource is deleted they get automatically cleaned up by Kubernetes. You could make the Ingress a child of the Service so that it gets cleaned up automatically.

# Here's an example in Python, you could equally do this with kubectl
from kr8s.objects import Service, Ingress

# Create your Ingress
ingress = Ingress({...})  # Your Ingress spec goes here
ingress.create()

# Make the Ingress a child of the Service
service = Service.get("your-cluster-service-name")
service.adopt(ingress)  # Now when the service gets deleted the Ingress will be deleted automatically

from dask-kubernetes.