error after rollback:

Error: couldn't find key MICROMETER_METRICS_STEP in ConfigMap airbyte-prod/airbyte-prod-airbyte-env

The error

Error: couldn't find key MICROMETER_METRICS_STEP in ConfigMap airbyte-prod/airbyte-prod-airbyte-env

indicates that the expected environment variable

MICROMETER_METRICS_STEP

is missing from your Airbyte environment ConfigMap after a rollback. This type of error is commonly seen when: - The Helm chart or Airbyte version you rolled back to does not define or template this variable in the ConfigMap. - There is a mismatch between the expected environment variables in your deployment manifests and what is actually present in the ConfigMap, often due to changes between Airbyte versions or custom

values.yaml

overrides. A similar issue has been reported in the Airbyte community, where missing keys in the ConfigMap (such as

STRICT_COMPARISON_NORMALIZATION_TAG

or other metrics-related variables) caused deployment failures after upgrades or rollbacks. The recommended approach is to ensure that your

values.yaml

and Helm chart version are in sync, and that any custom environment variables are either removed or properly defined for the version you are deploying. In some cases, removing custom

env_vars

from your

values.yaml

resolved the issue, especially if those variables are not supported or required in the version you rolled back to [Can't upgrade 1.4.0 -> 1.5.0 via argoCD - ComparisonError](https://github.com/airbytehq/airbyte/issues/62519). What you can do: - Check your

values.yaml

for any custom environment variables related to metrics and remove or update them as needed. - Make sure you are using the correct Helm chart version that matches your Airbyte deployment. - If the variable is not required for your use case, you can remove references to it from your deployment templates or values file. If you continue to see this error, you may need to manually add the missing key to the ConfigMap or ensure your deployment templates do not reference it, depending on your Airbyte version and configuration. If you need more specific guidance, please provide the Airbyte and Helm chart versions you are using, as well as any relevant customizations in your

values.yaml

file.