BRH-301: Extend hatchery to launch prismacloud containers (#2061)

uc-cdis · Nov 1, 2022 · 5c3ba19 · 5c3ba19
1 parent da2478d
commit 5c3ba19
Show file tree

Hide file tree

Showing 2 changed files with 21 additions and 0 deletions.
diff --git a/gen3/bin/kube-setup-hatchery.sh b/gen3/bin/kube-setup-hatchery.sh
@@ -82,6 +82,15 @@ if ! g3kubectl get sa "$saName" -o json | jq -e '.metadata.annotations | ."eks.a
     gen3 awsrole attach-policy "arn:aws:iam::aws:policy/AWSResourceAccessManagerFullAccess" --role-name ${roleName} --force-aws-cli || exit 1
 fi
 
+if [[ -f "$(gen3_secrets_folder)/prisma/apikey.json" ]]; then
+    ACCESSKEYID=$(jq -r .AccessKeyID "$(gen3_secrets_folder)/prisma/apikey.json")
+    SECRETKEY=$(jq -r .SecretKey "$(gen3_secrets_folder)/prisma/apikey.json")
+    if [[ ! -z "$ACCESSKEYID" && ! -z "$SECRETKEY" ]]; then
+        gen3_log_info "Found prisma apikey, creating kubernetes secret so hatchery can do prismacloud stuff.."
+        g3kubectl delete secret prisma-secret --ignore-not-found
+        g3kubectl create secret generic prisma-secret --from-literal=AccessKeyId=$ACCESSKEYID --from-literal=SecretKey=$SECRETKEY
+    fi
+fi
 
 g3kubectl apply -f "${GEN3_HOME}/kube/services/hatchery/hatchery-service.yaml"
 gen3 roll hatchery

diff --git a/kube/services/hatchery/hatchery-deploy.yaml b/kube/services/hatchery/hatchery-deploy.yaml
@@ -104,6 +104,18 @@ spec:
             valueFrom:
               fieldRef:
                 fieldPath: status.hostIP
+          - name: PRISMA_ACCESS_KEY_ID
+            valueFrom:
+              secretKeyRef:
+                name: prisma-secret
+                key: AccessKeyId 
+                optional: true
+          - name: PRISMA_SECRET_KEY
+            valueFrom:
+              secretKeyRef:
+                name: prisma-secret
+                key: SecretKey
+                optional: true
         volumeMounts:
           - name: hatchery-config
             readOnly: true