hotfix: added init containers in production

Author: Mautjee

k8s/production/aztec-listener/deployment.yaml

@@ -18,6 +18,23 @@ spec:
     spec:
       imagePullSecrets:
         - name: do-registry
+      initContainers:
+        - name: run-migrations
+          image: aztec-listener:latest
+          command: ["yarn", run, "migrate"]
+          env:
+            - name: NODE_ENV
+              value: "development"
+            - name: POSTGRES_IP
+              value: "postgresql"
+            - name: POSTGRES_PORT
+              value: "5432"
+            - name: POSTGRES_DB_NAME
+              value: "aztec_listener"
+            - name: POSTGRES_ADMIN
+              value: "admin"
+            - name: POSTGRES_PASSWORD
+              value: "secret-local-password"
       containers:
         - image: registry.digitalocean.com/aztlan-containers/aztec-listener:latest
           resources:

k8s/production/explorer-api/deployment.yaml

@@ -18,6 +18,23 @@ spec:
     spec:
       imagePullSecrets:
         - name: do-registry
+      initContainers:
+        - name: run-migrations
+          image: explorer-api:latest
+          command: ["yarn", run, "migrate"]
+          env:
+            - name: NODE_ENV
+              value: "development"
+            - name: POSTGRES_IP
+              value: "postgresql"
+            - name: POSTGRES_PORT
+              value: "5432"
+            - name: POSTGRES_DB_NAME
+              value: "explorer_api"
+            - name: POSTGRES_ADMIN
+              value: "admin"
+            - name: POSTGRES_PASSWORD
+              value: "secret-local-password"
       containers:
         - image: registry.digitalocean.com/aztlan-containers/explorer-api:latest
           resources: