To override the STATSD_PORT for Airbyte in a Kubernetes deployment, you can modify your

values.yaml

file and then upgrade your Helm release. Here's how you can do it: 1. Create or update your

values.yaml

file with the following configuration:

yaml global:   env_vars:     STATSD_PORT: "your_desired_port"

Replace "your_desired_port" with the actual port number you want to use. 2. After making this change to your

values.yaml

file, upgrade your Helm release using the following command:

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

This command will apply the new configuration to your Airbyte deployment, overriding the STATSD_PORT with your specified value. For more detailed information on customizing your Airbyte deployment, you can refer to the [Implementation Guide](https://docs.airbyte.com/enterprise-setup/implementation-guide#customizing-your-deployment). It's important to note that changing this value may affect how Airbyte interacts with your monitoring system. Make sure that the new port is correctly configured in your StatsD server or any other system that's expecting to receive metrics from Airbyte on this port.

It seems you're encountering an error related to duplicate entries for the STATSD_PORT configuration. This issue is likely caused by the STATSD_PORT being defined multiple times in your Kubernetes deployment configuration. Let's address this based on the information from our knowledge sources. This error is similar to an issue reported in the Airbyte GitHub repository. According to [Github Issue #43432](https://github.com/airbytehq/airbyte/issues/43432), duplicate entries in environment variables can cause deployment failures. To resolve this issue, you can try the following: 1. Check your

values.yaml

file and ensure that you're not defining STATSD_PORT multiple times. It should only be defined once, preferably in the global section as shown in the previous answer. 2. If you're using a recent version of Airbyte (0.429.0 or later), this issue should have been resolved. As mentioned in the GitHub issue: "Hi, we've removed the duplicate env vars as of 0.429.0. I tested and this should be working fine now." If you're using an older version, consider upgrading to the latest version of Airbyte. 3. If the issue persists, you may need to check other configuration files or deployment scripts to ensure STATSD_PORT is not being set in multiple places. 4. As a workaround, you could try removing the STATSD_PORT configuration from your custom

values.yaml

file and let Airbyte use its default value. Then, if needed, you can set this value through other means (like environment variables) after the deployment. If the problem continues after trying these steps, you might want to open an issue on the [Airbyte GitHub repository](https://github.com/airbytehq/airbyte/issues) with details about your deployment configuration and the exact error message you're seeing. Remember, when modifying your deployment, always use the command to upgrade your Helm release:

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

This will apply your changes and should resolve the duplicate entry issue if it's coming from your custom configuration.