From 1e79045a2ee65ed86750d91b94884230d4b1d3c5 Mon Sep 17 00:00:00 2001
From: YuviPanda <yuvipanda@gmail.com>
Date: Wed, 20 Mar 2024 18:48:44 -0700
Subject: [PATCH] Allow ESDIS hub access to S3

We were setting up the name of the service account in daskhub/values.yaml,
so hubs that were set up without dask don't actually have access to
the IAM roles set up for them!
---
 config/clusters/nasa-esdis/common.values.yaml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/config/clusters/nasa-esdis/common.values.yaml b/config/clusters/nasa-esdis/common.values.yaml
index 118e58b662..28ef1b85af 100644
--- a/config/clusters/nasa-esdis/common.values.yaml
+++ b/config/clusters/nasa-esdis/common.values.yaml
@@ -47,6 +47,10 @@ jupyterhub:
           - freitagb # Brian Freitag
           - slesaad # Slesa Adhikari
   singleuser:
+    # We want to access IAM roles here, even though this is not set up to use dask
+    cloudMetadata:
+      blockWithIptables: false
+    serviceAccountName: user-sa
     defaultUrl: /lab
     profileList:
       - display_name: "Modified Pangeo Notebook"