Open jkleinkauff opened 3 months ago
I have similar issue but with GCP, my logs are being pushed to GCS bucket but airflow UI can not read them. I see the following error on airflow UI.
*** No logs found in GCS; ti=%s <TaskInstance: xyz> *** Could not read served logs: [Errno -2] Name or service not known
Also I am new to helm, whats the correct way of passing these values to values.yaml:
airflow:
config:
AIRFLOW__LOGGING__REMOTE_LOGGING: "True"
AIRFLOW__LOGGING__REMOTE_BASE_LOG_FOLDER: "gs://airflow/logs"
AIRFLOW__LOGGING__REMOTE_LOG_CONN_ID: "my_conn"
connections:
- id: my_conn
type: google_cloud_platform
description: my GCP connection
When I add these values to values.yaml and run a helm upgrade, I see no changes happening to any pod/deployment.
+1 found workaround pass through creds as ENV https://github.com/airflow-helm/charts/discussions/833#discussioncomment-8617171
Checks
User-Community Airflow Helm Chart
.Chart Version
8.8.0
Kubernetes Version
Helm Version
Description
Hey folks! I'm bumping our Airflow version from 2.2.5 to 2.7.3. - I also upgraded the chart version to 8.8.0.
During this upgrade, it seems remote logging is not working anymore. I'm unsure in which version it stopped, tho.
My config:
in helm_release:
policy:
I know the logs are specific about the permissions, but there is more to it as this was the same setting it was working on before. I would love any tips, thank you friends!
Relevant Logs
Custom Helm Values