Summary
The user is trying to adjust the max memory for a worker pod in Airbyte via the values.yaml file but the settings do not seem to change. They have provided the values.yaml configuration and the output of kubectl get pods for reference.
Question
<@U01MMSDJGC9> + Anyone have success adjusting max memory for worker pod via the value.yaml file?
I have tried the below but the worker settings does not seem to change.
<VALUES.yaml>
global:
edition: “community”
jobs:
resources:
limits:
cpu: 1000m
memory: 12Gi ## e.g. 500m
requests:
cpu: 500m
memory: 2Gi
env_vars:
HTTP_IDLE_TIMEOUT: 1800s
webapp:
ingress:
annotations:
http://kubernetes.io/ingress.class|kubernetes.io/ingress.class: internal
http://nginx.ingress.kubernetes.io/proxy-body-size|nginx.ingress.kubernetes.io/proxy-body-size: 16m
http://nginx.ingress.kubernetes.io/proxy-send-timeout|nginx.ingress.kubernetes.io/proxy-send-timeout: 1800
http://nginx.ingress.kubernetes.io/proxy-read-timeout|nginx.ingress.kubernetes.io/proxy-read-timeout: 1800
airbyte-bootloader:
resources:
limits:
cpu: 1000m
memory: 12Gi ## e.g. 500m
requests:
cpu: 500m
memory: 2Gi
<end of file>
root@airbyte-abctl-control-plane:/# kubectl get pods --all-namespaces -o custom-columns=NAMESPACE:.metadata.namespace,NAME:.metadata.name,MEMORY_REQUEST:.spec.containers[].resources.requests.memory,MEMORY_LIMIT:.spec.containers[].resources.limits.memory
NAMESPACE NAME MEMORY_REQUEST MEMORY_LIMIT
airbyte-abctl airbyte-abctl-airbyte-bootloader 2Gi 12Gi
airbyte-abctl airbyte-abctl-connector-builder-server-5c6d48b574-tpm7h <none> <none>
airbyte-abctl airbyte-abctl-cron-5ddb45bc4d-swvcz <none> <none>
airbyte-abctl airbyte-abctl-pod-sweeper-pod-sweeper-7cbbf9cf6d-gfczc <none> <none>
airbyte-abctl airbyte-abctl-server-579f67894b-9m9ht <none> <none>
airbyte-abctl airbyte-abctl-temporal-d858d6866-zt6s4 <none> <none>
airbyte-abctl airbyte-abctl-webapp-7f5b9b7654-8bmdg <none> <none>
airbyte-abctl airbyte-abctl-worker-55cb9b56c5-mn945 <none> <none>
airbyte-abctl airbyte-abctl-workload-api-server-d64449cb8-czc2z <none> <none>
airbyte-abctl airbyte-abctl-workload-launcher-65854658f9-d57k9 <none> <none>
airbyte-abctl airbyte-db-0 <none> <none>
airbyte-abctl airbyte-minio-0 1Gi 1Gi
airbyte-abctl destination-snowflake-check-13151-1-ahqzk <none> <none>
airbyte-abctl replication-job-13151-attempt-0 2Gi,2Gi,2Gi 12Gi,12Gi,12Gi
airbyte-abctl replication-job-13152-attempt-0 2861Mi,2861Mi,2861Mi 2861Mi,2861Mi,2861Mi
airbyte-abctl replication-job-13153-attempt-0 2Gi,2Gi,2Gi 12Gi,12Gi,12Gi
airbyte-abctl source-mssql-check-13151-1-dbhgk <none> <none>
ingress-nginx ingress-nginx-controller-f884455f-6mm6f 90Mi <none>
kube-system coredns-76f75df574-8rgjj 70Mi 170Mi
kube-system coredns-76f75df574-sm72j 70Mi 170Mi
kube-system etcd-airbyte-abctl-control-plane 100Mi <none>
kube-system kindnet-wtvzx 50Mi 50Mi
kube-system kube-apiserver-airbyte-abctl-control-plane <none> <none>
kube-system kube-controller-manager-airbyte-abctl-control-plane <none> <none>
kube-system kube-proxy-gblfh <none> <none>
kube-system kube-scheduler-airbyte-abctl-control-plane <none> <none>
local-path-storage local-path-provisioner-888b7757b-ctzdk <none> <none>
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.