Closed dylac closed 1 year ago
@dylac it's going to be difficult to debug this without some logs, did you know that you can get the logs of failed containers using --previous
flag of kubectl get logs Pod/xxxxxxx --previous
?
Alternatively, I always recommend the k9s
CLI for managing Kubernetes, which exposes pod logs with the simple press of the L
key, and the previous logs with the press of the P
key.
Can you try and get the logs of the crashing pod for me?
This issue has been automatically marked as stale because it has not had activity in 60 days. It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.
Issues never become stale if any of the following is true:
lifecycle/frozen
label
Checks
User-Community Airflow Helm Chart
.Chart Version
8.6.1
Kubernetes Version
Helm Version
Description
I am trying to configure an EFS share as a destination for persistent logging. When I do the
helm upgrade --install
, the PVC shows as "Bound" to the correct PV and storageClass from the airflow pods' perspective, and I've tested that I can mount and write to it withextraVolumes
using a sample app from the AWS documentation, so I'm fairly sure it's not an AWS/EKS/non-helm issue at this point. The relevant part of my values.yaml overrides are in the appropriate section below.I've tried many different combinations of the relevant options, for example:
/opt/airflow/logs
for the path and mountPath instead of the custom one aboveextraVolumes
andextraVolumeMounts
only in a specific container i.e. worker, web, schedulerextraInitContainers
that doeschown -R 777 (logpath)
andchown -R 777 ${AIRFLOW_HOME}
(this was suggested as a fix in another somewhat similar issue)None of the above has helped. All containers except redis and pgbouncer (I'm using an external db with RDS) fail almost immediately with
Back-off restarting failed container
andCrashLoopBackOff
. This means there isn't much in the way of logs. Notably though, the efs-csi-controller containers don't show any attempt by the pods to mount the EFS share (they do when I used the AWS' docs sample app).If I just set
persistence: false
everything works fine; logs are written to the path. Just not to EFS.Feeling a bit stuck. Any advice is appreciated!
Relevant Logs
Custom Helm Values