mik-laj edited a comment on issue #17191: URL: https://github.com/apache/airflow/issues/17191#issuecomment-890873827
@potiuk Only in our case we do not have an ideal situation that is in line with the philosophy of K8s. In our case, one component performs two roles: webserver, tasks handling service. For webserver, it is more common to use an HTTP-based probe, but for the second type of service (which does not provide an HTTP endpoint), it is more natural to use exec probe. Kubernetes also does not allow us to define of two liveness probes for one container, so we have to decide which service we want to monitor directly and which we will monitor only as a child process from the main process. Alternatively, we can move the webserver to a new container/process that will allow us to [define a new probe](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes) for webserver and fully manage its lifetime in line with the Kubernetes philosophy. This will increase the complexity of deployment in environments that do not use Kubernetes and users "semi-automatically" run such processes. Separating these processes will also allow us to control the number of web servers regardless of the number of worker, but for now we have a fairly simple 1: 1 model, i.e. we always run only one web server per worker. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
