This message was deleted.
# ask-ai
s
This message was deleted.
k
The error message you're seeing is related to a version mismatch between your database and the jOOQ library used by Airbyte. The jOOQ library is used for constructing SQL queries in a type-safe way. The warning message indicates that your PostgreSQL database version (13.15) is older than what the jOOQ dialect for PostgreSQL supports. You might want to consider upgrading your PostgreSQL version or using a version of jOOQ that supports your current PostgreSQL version. You can refer to the [jOOQ support matrix](https://www.jooq.org/download/support-matrix) to see which jOOQ version supports which RDBMS versions. The other log messages are just informational and indicate that Airbyte is using default values for various environment variables related to resource limits for Kubernetes. These are not related to the version mismatch warning. Please note that this is based on the information provided and does not include any code or specific steps to resolve the issue as the knowledge sources do not provide such information.
s
@kapa.ai how to change the defaault environment value using helm?
k
A message from kapa.ai
To change the default environment values using Helm, you need to create a
values.yaml
file and specify your own configuration. This file should be located in the local folder and populated with the default configuration override values. Here is an example of how you can do it: 1. Create a
values.yaml
file in your local directory. 2. Populate it with the default configuration override values. For example:
Copy code
yaml global:   env_vars:     SIDECAR_KUBE_CPU_LIMIT: '3.0'     SIDECAR_KUBE_CPU_REQUEST: '0.2'
3. After specifying your own configuration, run the following command:
Copy code
bash helm install --values path/to/values.yaml %release_name% airbyte/airbyte
Replace
path/to/values.yaml
with the path to your
values.yaml
file and
%release_name%
with the name of your Helm release. You can find an example of a
values.yaml
file in the [charts/airbyte](https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte/values.yaml) folder of the Airbyte repository. Please note that the specific environment variables and their values you need to set depend on your specific use case and requirements. For more information, refer to the [Airbyte documentation on deploying Airbyte on Kubernetes using Helm](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#custom-deployment).
A message from kapa.ai
To set up the
JOB_MAIN_CONTAINER_*
environment variables in Helm, you can specify them in the
values.yaml
file under the
global
section. Here's an example of how you can do it: 1. Create a
values.yaml
file in your local directory. 2. Populate it with the configuration override values. For example:
Copy code
yaml global:   jobs:     resources:       requests:         cpu: '0.5' # 50% of a single core         memory: '2Gi' # 2 gigabytes       limits:         cpu: '1' # 100% of a single core         memory: '4Gi' # 4 gigabytes
In this example,
JOB_MAIN_CONTAINER_CPU_REQUEST
is set to '0.5' (50% of a single core),
JOB_MAIN_CONTAINER_CPU_LIMIT
is set to '1' (100% of a single core),
JOB_MAIN_CONTAINER_MEMORY_REQUEST
is set to '2Gi' (2 gigabytes), and
JOB_MAIN_CONTAINER_MEMORY_LIMIT
is set to '4Gi' (4 gigabytes). 3. After specifying your own configuration, run the following command:
Copy code
bash helm install --values path/to/values.yaml %release_name% airbyte/airbyte
Replace
path/to/values.yaml
with the path to your
values.yaml
file and
%release_name%
with the name of your Helm release. Please note that the specific values you need to set depend on your specific use case and requirements. For more information, refer to the [Airbyte documentation on deploying Airbyte on Kubernetes using Helm](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#custom-deployment) and the [discussion on the Airbyte forum](https://github.com/airbytehq/airbyte/issues/35749).