@kapa.ai How following error can be resolved via values.yaml file? message='Airbyte could not track the sync progress. Sync process exited without reporting status.', type='io.airbyte.workers.exception.WorkloadMonitorException', nonRetryable=false

Based on the knowledge sources provided, there isn't specific information about resolving the exact error message you mentioned. However, I can provide some general guidance on how to address similar issues using the

values.yaml

file in Airbyte deployments. The error you're encountering suggests that there might be resource constraints or configuration issues preventing the sync process from completing successfully. To address this, you can try adjusting the resource allocations and other settings in your

values.yaml

file. Here are some suggestions: 1. Increase resource allocations: According to [this GitHub issue](https://github.com/airbytehq/airbyte/issues/48816), increasing the resources for jobs can help resolve OOM (Out of Memory) issues. You can try adjusting the

values.yaml

file like this:

yaml    jobs:      resources:        requests:          cpu: 500m          memory: 1Gi        limits:          cpu: 500m          memory: 1Gi

2. Configure workload launcher: [Another GitHub issue](https://github.com/airbytehq/airbyte/issues/48809) suggests adding specific environment variables to the workload-launcher pod. You can add these to your `values.yaml`:

yaml    workload-launcher:      env_vars:        AWS_ASSUME_ROLE_SECRET_NAME: airbyte-config-secrets        AWS_SECRET_MANAGER_ACCESS_KEY_ID_REF_NAME: airbyte-config-secrets        AWS_SECRET_MANAGER_ACCESS_KEY_ID_REF_KEY: aws-secret-manager-access-key-id        AWS_SECRET_MANAGER_SECRET_ACCESS_KEY_REF_NAME: airbyte-config-secrets        AWS_SECRET_MANAGER_SECRET_ACCESS_KEY_REF_KEY: aws-secret-manager-secret-access-key

3. Use a minimal `values.yaml`: According to the [Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/#3-create-a-valuesyaml-override-file), it's recommended to use a minimal

values.yaml

file with only the specific overrides you need, rather than copying the entire default file. After making these changes, you should apply the updated

values.yaml

file using the Helm upgrade command:

helm upgrade --namespace airbyte --values ./values.yaml --install airbyte airbyte/airbyte

If the issue persists after these changes, you may need to investigate further by examining the full sync logs or reaching out to Airbyte support for more specific assistance.