GitHub user PrithwishDas101 deleted a comment on the discussion: Airflow 2.9.3 version integration vault backend_kwargs
For this setup, I'd start by separating Vault connectivity from Airflow's secrets-backend configuration. A few checks can help isolate the issue: 1. Verify that the Airflow pods can reach Vault over HTTPS and that the certificate chain is trusted by the Airflow container. 2. Confirm that the configured secrets backend class and `backend_kwargs` match the Airflow 2.9.3 documentation, rather than copying configuration from a newer Airflow release. 3. Check the Vault mount point, secret path, and KV engine version. A path mismatch or KV v1/v2 difference can look like a permissions issue. 4. Verify that the Vault policy grants access to the exact paths Airflow requests, and inspect the Airflow logs for the underlying HTTP status rather than relying only on a missing connection result. 5. Keep bootstrap secrets separate from connections and variables retrieved through Airflow's secrets backend; the latter does not automatically configure the database or broker used to start Airflow itself. If you share the backend configuration with credentials redacted and the relevant error message, it should be easier to pinpoint whether this is a path, permission, TLS, or version-compatibility issue. GitHub link: https://github.com/apache/airflow/discussions/61669#discussioncomment-18950012 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
