The following error is preventing Helm managed worker pods starting after the release of Airbyte v0.50.32

couldn't find key USE_STREAM_CAPABLE_STATE in ConfigMap default/airbyte-airbyte-env: CreateContainerConfigError

Based on the information provided in the extracts, it seems like the error you're encountering is due to a missing key in the ConfigMap. This is similar to the issue mentioned in the [forum post](https://discuss.airbyte.io/t/3221) where the

airbyte-worker

pod was failing due to a missing

CONTAINER_ORCHESTRATOR_IMAGE

key in the ConfigMap. The solution in that case was to add the missing key in the

.env

file located in

kube/overlays/stable-with-resource-limits/

. In your case, you might need to add the

USE_STREAM_CAPABLE_STATE

key to your ConfigMap. However, the exact location and value to use for this key is not provided in the extracts. For more detailed instructions on how to configure your Airbyte deployment, you can refer to the [Configuring Airbyte](https://docs.airbyte.com/operator-guides/configuring-airbyte) section in the documentation. If you're using a Kubernetes deployment, you would typically modify the

values.yaml

file as described in the [Custom deployment](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#custom-deployment) section. If the issue persists, I would recommend reaching out to the Airbyte community on their [forum](https://discuss.airbyte.io) or [Slack](https://airbytehq.slack.com) for further assistance.