Hi folks, We currently deploy Airflow on Kubernetes (using custom image, migrating to official image is planned) and we use Local executor (changing to Kubernetes executor also in plans). We meet the following problem: For cost efficiency, our testing cluster is scaled down every night. Then every morning the pod running airflow is up, but not healthy. The issue comes from the way we start scheduler and webserver. Since they are 2 processes, we should have something like supervisord to handle them.
Now my question is, given that we have a check-health <https://airflow.apache.org/docs/stable/howto/check-health.html>, how could it be used in liveness/probe check from k8 so it understands that pod is not healthy any more and it should redeploy it? Have others met similar issues? If so how did you approach? Sergio.
