Scott Henderson

Thanks @jhamman and @yuvipanda for the pointers! I'm looping in @TomAugspurger and @jacobtomlinson b/c this is relevant to dask-kubernetes

This might be related.. long start up times are partly due to continuous-image-puller being enabled - When new user or dask nodes are added **all** of the images in profileList...

This is coming up as an issue currently during our icesat2 hackweek at UW. People often want to move large amounts of files TO and FROM the hub. For now,...

Good ideas @apawloski. We originally had S3 accesses limited to the VPC, but users want to upload data from their laptops or servers at all kinds of IP addresses. Many...

> Of course none of this addresses the namespacing situation where one user doesn’t want other users to have access their data in S3.. True. There are two separate issues...

Thanks for looking into this Tom! > Ideally users would only be able to see (and not modify) objects related to their own pods. I suspect that isolating users from...

this would be awesome! let's do it

Also, @TomAugspurger just to clarify, same error seems to occur on GCP, but not your pangeo gallery example, so perhaps this is an issue coming up with more recent dask...

I'm also noticing the jupyterlab interface has a lot of lag, and even without connecting to a dask cluster, i'm seeing lots of repeated 404 errors in the javascript console...

Ok, I think a lot of these network errors happening behind the scenes are maybe red herrings and fairly normal. I realized the main problem was I had some old...