Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Hi, I am running into the below while deploying airbyte on kubernetes. This is on airbyte/worker:0.40.23. Have checked everything but not able to get around this. Any help is appreciated.
```Message: Index 1 out of bounds for length 1
Path Taken: new ApplicationInitializer() --&gt; ApplicationInitializer.checkConnectionActivities --&gt; List.checkConnectionActivities([CheckConnectionActivity checkConnectionActivity]) --&gt; new CheckConnectionActivityImpl(WorkerConfigs workerConfigs,ProcessFactory processFactory,SecretsHydrator secretsHydrator,Path workspaceRoot,WorkerEnvironment workerEnvironment,LogConfigs logConfigs,[AirbyteApiClient airbyteApiClient],String airbyteVersion,AirbyteMessageSerDeProvider serDeProvider,AirbyteMessageVersionedMigratorFactory migratorFactory)
io.micronaut.context.exceptions.BeanInstantiationException: Error instantiating bean of type  [io.airbyte.workers.temporal.check.connection.CheckConnectionActivityImpl]```

Are you deploying with helm or kustomize?

I am deploying it in own compute cluster, -&gt; pulling images, tag , push and creating the spec (yaml) by tying all the services running together in one pod

Here is the env variables I am setting in spec :
```  env:        
        AIRBYTE_VERSION: "0.40.23"
        CONFIG_ROOT: /data
        DATABASE_HOST: localhost
        DATABASE_USER: postgres
        DATABASE_PASSWORD: test123
        DATABASE_URL: jdbc:<postgresql://localhost:5432/airbyte>
        DATABASE_PORT: 5432
        DATABASE_DB: airbyte
        TRACKING_STRATEGY: segment
        TEMPORAL_WORKER_PORTS: 8080
        LOG_LEVEL: DEBUG
        MICRONAUT_ENVIRONMENTS: control-plane
        SHOULD_RUN_NOTIFY_WORKFLOWS: false
        INTERNAL_API_HOST: "127.0.0.1"
        WORKSPACE_ROOT: /tmp/workspace
        TEMPORAL_HOST: airbyte-temporal:7233
        WEBAPP_URL: "<http://localhost:8000/>"
        MAX_SYNC_WORKERS: 5
        MAX_SPEC_WORKERS: 5
        MAX_CHECK_WORKERS: 5
        MAX_DISCOVER_WORKERS: 5
        MAX_NOTIFY_WORKERS: 5
        JOBS_DATABASE_MINIMUM_FLYWAY_MIGRATION_VERSION: 0.29.15.001
        WORKER_LOGS_STORAGE_TYPE: MINIO
        WORKER_STATE_STORAGE_TYPE: MINIO
        STATE_STORAGE_MINIO_BUCKET_NAME: airbyte-dev-logs 
        STATE_STORAGE_MINIO_ENDPOINT: "<http://airbyte-minio-svc:9000>"
        STATE_STORAGE_MINIO_ACCESS_KEY: minio
        STATE_STORAGE_MINIO_SECRET_ACCESS_KEY: minio123
        CONFIG_DATABASE_USER: postgres
        CONFIG_DATABASE_PASSWORD: test123
        CONFIG_DATABASE_URL:  "jdbc:<postgresql://localhost:5432/airbyte>"```
TIA

Let me look into this, as this does not use one of our documented approaches - it may take longer!

Thank you <@U03J7N20YAF>. Though this is not documented, I pretty much followed how kustomize overlay all the layers with all env variables in the yaml spec

Please let me know what is the cause for this issue. I have posted the spec already, this is happening in 0.40.23 version.

Hi, <@U04CBDEHE8M>! Apologies for the wait! Were you able to figure this out?