Support explicit bind address for worker log server #60117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Currently, the Airflow worker log server (serve_logs.py) is hardcoded to bind to all available interfaces (0.0.0.0 or [::]) via socket.has_dualstack_ipv6(). This exposes port 8793 to the entire network by default, creating a potential security risk where task logs could be intercepted or scanned by unauthorized entities.
Proposed Change
This PR modifies the log server initialization to respect the WORKER_LOG_SERVER_HOST configuration variable. If this variable is set (e.g., to 127.0.0.1), the server will bind specifically to that address. If not set, it falls back to the existing dual-stack wildcard logic to maintain backward compatibility.