When starting a suspended instance that the user has been adding nodes to over time it may fail because npm consumes more memory than the container allows (k8s/docker)
On these platforms we are now passing the memory/cpu limits to the nr-launcher as a env var, we should be able to use this to set the NODE_OPTIONS env var for the npm process to limit the memory used. This should stop npm getting killed by the container manager.
Description
When starting a suspended instance that the user has been adding nodes to over time it may fail because npm consumes more memory than the container allows (k8s/docker)
On these platforms we are now passing the memory/cpu limits to the nr-launcher as a env var, we should be able to use this to set the NODE_OPTIONS env var for the npm process to limit the memory used. This should stop npm getting killed by the container manager.