[ https://issues.apache.org/jira/browse/AIRFLOW-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393063#comment-16393063 ]
Semet commented on AIRFLOW-1084: -------------------------------- Hello. I maintain an Airflow chart for Kubernetes, and most endpoint does not have a livenessprobe: - [Scheduler does not have any|https://github.com/gsemet/kube-airflow/blob/master/airflow/templates/deployments-scheduler.yaml] - [Web UI have a /health|https://github.com/gsemet/kube-airflow/blob/master/airflow/templates/deployments-web.yaml] - [Worker does not|https://github.com/gsemet/kube-airflow/blob/master/airflow/templates/statefulsets-workers.yaml] - [Flower does not|https://github.com/gsemet/kube-airflow/blob/master/airflow/templates/deployments-flower.yaml] (only relevant for celery executor) > `/health` endpoint on each component > ------------------------------------ > > Key: AIRFLOW-1084 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1084 > Project: Apache Airflow > Issue Type: Improvement > Reporter: Semet > Priority: Major > > Please provide a {{/health}} endpoint of each of the following component: > - webservice (to avoid pinging the {{/}} root endpoint) > - worker > - scheduler > This would ease integration in Mesos/Marathon framework. > If you agree, I volunteer to add this change. -- This message was sent by Atlassian JIRA (v7.6.3#76005)