Post‑Deployment Checks

Verify Cosine is operational

It can take a few minutes for the database and pods to become ready, so give the cluster a moment before checking.

kubectl get pods

NAME                                                  READY   STATUS    RESTARTS   AGE
api-5cb8675c6-vvs2l                                   1/1     Running   0          21m
ccode-74fdd8d49b-h44xc                                1/1     Running   0          17h
ccode-node-mount-rpbh2                                1/1     Running   0          18m
dashboard-64dfbdd96c-h8bzw                            1/1     Running   0          22m
ingress-nginx-controller-controller-c466bdd6d-4csd8   1/1     Running   0          22m
mysql-85d4c95945-pvzbv                                1/1     Running   0          19h
parser-7848ff6f56-xpzkn                               1/1     Running   0          147m
redis-6f756c9767-ltjfh                                1/1     Running   0          19h
worker-55bb788758-56j45                               1/1     Running   0          17h

Verify database migrations

Check the migrations agent logs by shelling into the api pod and looking at startup.log:

kubectl exec -it <pod-name> -- /bin/bash
cat startup.log

If you see logs like the following, migrations did not run successfully:

Error during migration run:
AggregateError [ECONNREFUSED]:
    at internalConnectMultiple (node:net:1139:18)
    at afterConnectMultiple (node:net:1714:7) {
  code: 'ECONNREFUSED',
  ...
}

Common causes include:

Database misconfiguration
Missing permissions on the api pod
The database not being ready when the api pod started

You can re‑run the migrations manually if you need to bring the schema up to date. From within the api pod, run:

LOAD_MIGRATIONS=true CI=true ./node_modules/.bin/typeorm migration:run --dataSource ./dist/src/database/config/appdb.config.js --transaction=each