Proposed Dask architecture #163
                
     Draft
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    


what I would like to have:
a. use latest dask gateway helm chart that includes dask-gateway-server 2025.4.0 and traefik 3.3.5. No rs-python customization
b. use the smallest possible custom dask images for our three clusters, all based from latest dask-gateway 2025.4.0 (not server !):
i. l0: add only latest L0 (1.2.0), with compatible cpm (2.5.5) and compatible dask & dask-distributed (2024.5.2)
ii. s1-ard: add only latest s1_l12rp ard fork, with compatible cpm (2.5.9) and compatible dask & dask-distributed (2024.5.2)
iii. staging: add only latest rs_server_staging (1.0a1) and latest version of dask & dask-distributed (2025.7.0)
a. no dask-gateway-server at all
b. same images for local dask clusters than those running on kubernetes cluster