Yuvi

After writing https://github.com/pangeo-data/pangeo-docker-images/pull/355/files#diff-a77643b43a7be453fa8556937bf32b27907e152a10d4c693f3e7670c66a44378, I would like to ask that we reconsider *requiring* entrypoint be set to a specific thing (`jupyterhub-singleuser`) in the images users are required to produce. This makes...

I've missed these amazingly thought out and researched issues when I've been out, @consideRatio

Based on https://github.com/kubernetes-sigs/descheduler/blob/master/pkg/descheduler/strategies/pod_antiaffinity.go#L100 descheduler doesn't care about soft anti affinity, so isn't useful for us.

> This system is very much like how GPU nodes are handled, they are not made available until they have got their GPU devices attached and drivers installed. This requires...

More discussion about exactly our needs in https://github.com/kubernetes/kubernetes/issues/75890

And a possible implementation coming in a future k8s version :) https://github.com/kubernetes/enhancements/pull/1003

I agree! I'm currently running the following in a loop: ```python # Get all nodes from kubernetes import client, config config.load_kube_config() v1 = client.CoreV1Api() namespace = 'datahub-prod' attractor_label = 'hub.jupyter.org/attract-placeholders'...

I'm deploying https://github.com/berkeley-dsep-infra/datahub/pull/1050 now, will keep you posted on how it goes! It isn't a long term solution, just a fix for now.

I've now removed my workaround in https://github.com/berkeley-dsep-infra/datahub/pull/1657, since it was complex and difficult to use.

A while ago, I drew a diagram that might be useful: https://discourse.jupyter.org/t/jupyterhub-traffic-flows-how-they-are-secured/1246