I apologize for the confusion. You're correct. Your Airbyte platform version

v0.44.5

is indeed more recent than

v0.40.0-alpha

. In terms of upgrading, you should be up-to-date with your Airbyte platform. However, it's always a good practice to check for any newer versions periodically to ensure you have the latest features and improvements. You can refer to the [upgrade guide](https://docs.airbyte.com/operator-guides/upgrading-airbyte/) for the process when a new version is available. As for the Zendesk Support connector, without specific version information in the extracts provided, I can't confirm the latest version or the process to upgrade it. You should check the Airbyte documentation or the connector's settings in your Airbyte dashboard for this information.

I understand you're looking for guidance on upgrading Airbyte when it's deployed on Kubernetes using the official Helm chart. Based on the extracts provided, here's a general process you can follow: 1. Update your Helm repository: Before you start the upgrade process, make sure your Helm repository is up-to-date. You can do this by running the following command:

bash helm repo update

2. Upgrade Airbyte: If you have a

values.yaml

file with your configuration, you can upgrade Airbyte using the following command:

bash helm upgrade -f 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 this is a general process and might not cover all specific cases. Always make sure to backup your data and test the upgrade in a non-production environment first. For more detailed instructions or if you encounter any issues, please refer to the [official Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm) or reach out to the Airbyte community on [Slack](https://slack.airbyte.io/) or [GitHub](https://github.com/airbytehq/airbyte/issues/new?assignees=&labels=type%2Fbug&template=bug-report.md&title=).

I'm sorry to hear that you're experiencing the same issue as mentioned in the GitHub issue [#22197](https://github.com/airbytehq/airbyte/issues/22197). Based on the extracts provided, I don't have specific information on how to resolve this issue. However, here are a few general steps you can take: 1. Check the logs: The logs can provide detailed information about what's happening behind the scenes, and they can help pinpoint the root cause of the problem. 2. Reach out to the community: The Airbyte community forum and the Slack channel are great places to ask for help, share your experiences, and learn from others who have faced similar issues. 3. Open a Github ticket: If you're still unable to resolve the issue after reaching out to the community, it's time to open a support ticket. The Airbyte support team is here to help you with any issues you're facing with Airbyte. Remember to provide as much detail as possible when reaching out for help, including the version of Airbyte you're using, the specific connector and its version, any error messages or logs, and the steps to reproduce the issue. For more detailed troubleshooting steps, you can refer to the [Airbyte troubleshooting guide](https://docs.airbyte.com/troubleshooting).

There have been big changes in the way normalization works recently which may be related.