Export Job to IRSA

[EliseCastle23]

changing the export job to use environment variables and IRSA instead of access keys

Add these:

"serviceAccountName": "batch-export-sa"...


      - name: BUCKET
        valueFrom:
           configMapKeyRef:
            name: batch-export-g3auto
            key: bucket_name

Remove the following:

       "volumeMounts": [
          {
            "name": "batch-export-creds-volume",
            "readOnly": true,
            "mountPath": "/batch-export-creds.json",
            "subPath": "config.json"
          }
        ],
      },
      "volumes": [
        {
          "name": "batch-export-creds-volume",
          "secret": {
            "secretName": "batch-export-g3auto"
          }
        }
      ],

Improvements

changing the batch export job to use IRSA instead of access keys. Also, changing the job to use environment variables to read in the bucket name for the batch export job.

Deployment changes

Manifest.json files MUST be changed to use the new "batch-export-sa" service account and the "BUCKET" environment variable must be set to the batch-export-g3auto secret with the "bucket_name" key. You also no longer need to mount the batch-export-g3auto secret as this is now deprecated (it is replaced by the batch-export-g3auto configmap).

[mfshao]

👍