search

airbytehq / airbyte

The leading data integration platform for ETL / ELT data pipelines from APIs, databases & files to data warehouses, data lakes & data lakehouses. Both self-hosted and Cloud-hosted.
https://airbyte.com
Other
16.37k stars 4.16k forks source link

Orchestrator pod not taking and passing on all enviroment variables. #38183

Open ro8inmorgan opened 6 months ago

ro8inmorgan commented 6 months ago

Helm Chart Version

0.67.17

What step the error happened?

During the Sync

Relevant information

The orchestrator pod doesn't seem to read all enviroment variables and neither passes these on to the read and write pods. For example SOCAT_CPU_REQUEST and SIDECAR_CPU_REQUEST are not read by the orchestrator and so the read and write pods end up using the default values.

Relevant log output

2024-05-14 09:41:30 replication-orchestrator > Using default value for environment variable SIDECAR_KUBE_MEMORY_LIMIT: '50Mi'
2024-05-14 09:41:30 replication-orchestrator > Using default value for environment variable SIDECAR_MEMORY_REQUEST: '25Mi'
2024-05-14 09:41:30 replication-orchestrator > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: '2.0'
2024-05-14 09:41:30 replication-orchestrator > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: '0.1'
2024-05-14 09:41:30 replication-orchestrator > Using default value for environment variable SIDECAR_KUBE_MEMORY_LIMIT: '50Mi'
2024-05-14 09:41:30 replication-orchestrator > Using default value for environment variable SIDECAR_MEMORY_REQUEST: '25Mi'
2024-05-14 09:41:30 replication-orchestrator > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: '2.0'
2024-05-14 09:41:30 replication-orchestrator > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: '0.1'
2024-05-14 09:41:30 replication-orchestrator > Using default value for environment variable SIDECAR_KUBE_MEMORY_LIMIT: '50Mi'
2024-05-14 09:41:30 replication-orchestrator > Using default value for environment variable SIDECAR_MEMORY_REQUEST: '25Mi'
octavia-squidington-iii commented 3 days ago

At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.