0

I been deploying a NodeJs server to GKE without problems for some time. The app is a simple node server

The docker final command just invokes the start script: CMD ["node", "scripts/start.js"]

The deployment is done via gcloud deploy and everything is green (node, pod, ...) After a seamlessly trivial ui change, the pod hangs while executing the script... Even a small subset of sync code (esm imports) seems to also trigger the program to hang.

Extra context:

  • The very same docker image and config is deployed in another cluster (dont want to touch it for now).
  • In very rare cases after trying things up and down the process actually starts
  • There is no memory or cpu spikes and the node process is idle.
  • Resources seem to be more than enough on the pool/node

Anyone has any idea where can the problem be? Feel to be that there is something in the kubernetes cluster that is f-ed as its highly unlike is the code in itself...

Improve this question

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.