potiuk commented on issue #16039: URL: https://github.com/apache/airflow/issues/16039#issuecomment-849391020
Agree. I think there is never a need to override the port. Kubernetes networking model make each POD has different IP address and you can have many pods listening on the same port even if they are running on the same machine in the cluster - and the way how you expose the port to outside world via ingress maps the external port to internal service/port number. I'd rather stick to non-configurable port for Airflow Chart. Same with the health-check. Health-check is mostly for the internal kubernetes cluster management. You can still expose it to outside world on any port (And in our case, port of health-check of webserver is the same as the webserver one - so by exposing webserver your are alsoi exposing the health-check. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
