Thiago Guimarães
06/07/2023, 8:03 PMkapa.ai
06/07/2023, 8:03 PMkapa.ai
06/07/2023, 8:04 PMJOB_KUBE_TOLERATIONS and node selector settings in your Kubernetes deployment using Helm. To resolve this issue, make sure you have properly set the JOB_KUBE_TOLERATIONS and JOB_KUBE_NODE_SELECTORS in your values.yaml file. Here's an example of how to set these values: yaml global: jobs: tolerations: - key: <http://k8s.company.com/node-pool|k8s.company.com/node-pool> value: data operator: Equal nodeSelectors: key1: value1 key2: value2 After updating your values.yaml file, upgrade your Helm chart by running the following command: bash helm upgrade -f path/to/values.yaml %release_name% airbyte/airbyte If you still face issues, please refer to this [forum discussion](https://discuss.airbyte.io/t/2153) where a user faced a similar issue and resolved it by properly setting the taint on the node and using the JOB_KUBE_NODE_SELECTORS and JOB_KUBE_TOLERATIONS variables. For more information on configuring Airbyte on Kubernetes, you can refer to the [official documentation](https://docs.airbyte.com/operator-guides/configuring-airbyte).