Skip to content

Conversation

bartoszmajsak
Copy link
Contributor

This change is made to support environments that require HTTPS. The server can now run over HTTPS with either user-provided certs or self-signed ones.

This is done through flags aligned with vLLM (--ssl-certfile, --ssl-keyfile). Additionally --self-signed-certs has been provided for self-signed certs.

@bartoszmajsak bartoszmajsak force-pushed the tls_listener branch 3 times, most recently from d70f576 to 5f4be3f Compare September 18, 2025 08:26
@irar2 irar2 requested a review from shmuelk September 18, 2025 08:26
This change is made to support environments that require HTTPS. The
server can now run over HTTPS with either user-provided certs or
self-signed ones.

This is done through flags aligned with vLLM (`--ssl-certfile`, `--ssl-keyfile`).
Additionally `--self-signed-certs` has been provided for self-signed certs.

Signed-off-by: Bartosz Majsak <[email protected]>
@shmuelk
Copy link
Collaborator

shmuelk commented Sep 18, 2025

/lgtm

/approve

@github-actions github-actions bot added the lgtm label Sep 18, 2025
@github-actions github-actions bot merged commit 4b961c7 into llm-d:main Sep 18, 2025
4 checks passed
@bartoszmajsak bartoszmajsak deleted the tls_listener branch September 18, 2025 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants