Summary
The user is inquiring about potential changes in Helm charts that may prevent the replication job from triggering a node scale-up, despite having allocated sufficient resources.
Question
Was there a change in the helm charts that the replication job doesnt trigger a node scale up?
Background:
I have started a node with 16 GB and 4 CPU and still getting insufficient memory and cpu when this pod is started, replication-job-10-attempt-0.
This is a bit weird, maybe im not familiar with a setting in kubernetes but it doesnt make sense for me currently.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.