Summary
The user is facing an issue where the resource settings for the read pod in Airbyte setup on GCP using Helm are not being picked up as expected.
Question
Hi AirByte folks,
I’m running into a bit of a snag with my AirByte setup (v0.50.45) on GCP using Helm.
My read pod isn’t picking up the resource settings I’ve put in place.
What I’ve set up:
• JOB_MAIN_CONTAINER_CPU_LIMIT: 4000m
• JOB_MAIN_CONTAINER_CPU_REQUEST: 4000m
• JOB_MAIN_CONTAINER_MEMORY_LIMIT: 4Gi
• JOB_MAIN_CONTAINER_MEMORY_REQUEST: 4Gi
But here’s what I’m seeing:
• Check Pod seems (main container) to be in order ( CPU is at 4050m and Memory at 4533Mi)
• Read Pod: CPU is at 2190m and Memory at 2741Mi, which is less than my settings.
I’m scratching my head trying to figure out why my read pod’s getting less resources than what I’ve set. Any ideas why this might be happening or how I can fix it?
Cheers!
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.