airbyte-worker pod fails to start on version 0.50.33 with micronaut error

2023-10-28 13:43:28.257 CST
Caused by: java.lang.IllegalArgumentException
2023-10-28 13:43:28.257 CST
	at com.google.common.base.Preconditions.checkArgument(Preconditions.java:131) ~[guava-31.1-jre.jar:?]
2023-10-28 13:43:28.257 CST
	at com.google.api.client.util.Preconditions.checkArgument(Preconditions.java:35) ~[google-http-client-1.43.1.jar:1.43.1]
2023-10-28 13:43:28.257 CST
	at io.airbyte.config.storage.DefaultGcsClientFactory.validate(DefaultGcsClientFactory.java:32) ~[io.airbyte.airbyte-config-config-models-0.50.33.jar:?]
2023-10-28 13:43:28.257 CST
	at io.airbyte.config.storage.DefaultGcsClientFactory.<init>(DefaultGcsClientFactory.java:27) ~[io.airbyte.airbyte-config-config-models-0.50.33.jar:?]
2023-10-28 13:43:28.257 CST
	at io.airbyte.workers.storage.GcsDocumentStoreClient.create(GcsDocumentStoreClient.java:34) ~[io.airbyte-airbyte-commons-worker-0.50.33.jar:?]
2023-10-28 13:43:28.257 CST
	at io.airbyte.workers.storage.StateClients.create(StateClients.java:33) ~[io.airbyte-airbyte-commons-worker-0.50.33.jar:?]
2023-10-28 13:43:28.257 CST
	at io.airbyte.workers.config.ContainerOrchestratorConfigBeanFactory.kubernetesContainerOrchestratorConfig(ContainerOrchestratorConfigBeanFactory.java:91) ~[io.airbyte-airbyte-workers-0.50.33.jar:?]
2023-10-28 13:43:28.257 CST
	at io.airbyte.workers.config.$ContainerOrchestratorConfigBeanFactory$KubernetesContainerOrchestratorConfig0$Definition.build(Unknown Source) ~[io.airbyte-airbyte-workers-0.50.33.jar:?]

Hmm, I don't know enough to give you a confident answer yet. The error message you provided seems to be related to Google Cloud Storage (GCS) configuration, but the information extracts provided do not contain specific details about this error or how to resolve it. However, based on the extracts, it seems that some users have encountered similar issues with the

airbyte-worker

pod failing to start due to various reasons. Some of these issues were resolved by upgrading Airbyte to the latest version, adjusting environment variables, or modifying the deployment configuration. I recommend checking your GCS configuration and ensuring that it is correctly set up. Also, make sure you are using the latest version of Airbyte and that your deployment configuration is correct. For more detailed guidance, you may want to refer to the [Airbyte documentation](https://docs.airbyte.com) or ask for help in the [Airbyte community forum](https://discuss.airbyte.io).

@kapa.ai Does Airbyte still support state storage in GCS?

Hmm, I don't know enough to give you a confident answer yet. The extracts provided do not contain specific information about Airbyte's support for state storage in Google Cloud Storage (GCS). However, Airbyte does support syncing data to GCS buckets, and each data stream is written to its own directory under the bucket [source](https://docs.airbyte.com/integrations/destinations/gcs). For more detailed information, you may want to check the official Airbyte documentation or reach out to the Airbyte community.