@kapa.ai airbyte downgrade to 0.58.0 on K8s is failing with temporal crashloopbackoff. The error is "Unable to start server. Error: could not build arguments for function "go.temporal.io/server/common/pprof".LifetimeHooks (/home/builder/temporal/common/pprof/fx.go:39): failed to build *pprof.PProfInitializerImpl: could not build arguments for function "go.temporal.io/server/common/pprof".NewInitializer (/home/builder/temporal/common/pprof/pprof.go:56): failed to build *config.PProf: received non-nil error from function "go.temporal.io/server/temporal".ServerOptionsProvider (/home/builder/temporal/temporal/fx.go:152): sql schema version compatibility check failed: pq: no pg_hba.conf entry for host "10.0.27.212", user "airbyte", database "temporal", no encryption"

The error you're encountering with Airbyte's temporal service on Kubernetes appears to be related to a database connection issue. Specifically, it's failing to connect to the PostgreSQL database due to a missing or incorrect entry in the pg_hba.conf file. This file controls client authentication for PostgreSQL. Based on the information provided in the knowledge sources, here are a few potential solutions you can try: 1. Enable SSL/TLS for the database connection: Try adding the following environment variables to your temporal configuration in the Helm values file [Github Issue #38593](https://github.com/airbytehq/airbyte/issues/38593):

yaml    temporal:      extraEnv:        - name: SQL_TLS_ENABLED          value: "true"        - name: POSTGRES_TLS_ENABLED          value: "true"        - name: POSTGRES_TLS_DISABLE_HOST_VERIFICATION          value: "true"

2. Check your PostgreSQL configuration: Ensure that your PostgreSQL server is configured to allow connections from the Kubernetes cluster's IP range. You may need to update the pg_hba.conf file on your PostgreSQL server to include the appropriate entries for your Kubernetes cluster's IP range [Github Issue #30484](https://github.com/airbytehq/airbyte/issues/30484). 3. Verify database connection details: Double-check that the database connection details (host, port, username, database name) in your Airbyte configuration are correct [Github Issue #26647](https://github.com/airbytehq/airbyte/issues/26647). 4. If you're using an external database (like AWS RDS), make sure that: - The security group allows incoming connections from your Kubernetes cluster. - The database parameter group is correctly configured [Github Issue #30484](https://github.com/airbytehq/airbyte/issues/30484). If these solutions don't resolve the issue, you may need to investigate further by looking at the logs of other Airbyte components and your PostgreSQL server logs to identify any additional error messages or configuration issues.