rdme: Update access for non-kms apps#306
Merged
Merged
Conversation
h4x3rotab
reviewed
Aug 21, 2025
| - `3327603e03f5bd1f830812ca4a789277fc31f577-8080s.app.kvin.wang` → port `8080` (TLS passthrough) | ||
|
|
||
| **Example**: `3327603e03f5bd1f830812ca4a789277fc31f577-8080.app.kvin.wang` maps to port `8080` in the CVM. | ||
| The `<id>` can be either the app ID or instance ID. When using the app ID, the load balancer will select one of the available instances. Adding an `s` suffix enables TLS passthrough to the app instead of terminating at dstack-gateway. Adding a `g` suffix enables HTTPS/2 with TLS termination for gRPC applications. |
Contributor
There was a problem hiding this comment.
Two questions:
- Is it only for gRPC, or also used for other http/2 applications?
- Is it necessary to have the
gsuffix?
Collaborator
Author
There was a problem hiding this comment.
- It's for all HTTP/2.
- Without
g, the gateway doesn't know HTTP/2 backend support. Falsely advertising HTTP/2 compatibility would result in the client sending incompatible packets to an HTTP/1.1 server.
Contributor
There was a problem hiding this comment.
Do you think it's better to use -h2 instead of -g? And for custom domain, does it detect the suffix in the TXT record?
Collaborator
Author
There was a problem hiding this comment.
*-8080-h2 would be a breaking change introducing another compatibility issue, *-8080h2 looks a bit weird to me.
And for custom domain, does it detect the suffix in the TXT record?
No, custom domain knows itself support h2 or not, it can only advertising h2 when the backend support it.
kvinwang
added a commit
that referenced
this pull request
Jan 19, 2026
rdme: Update access for non-kms apps
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updates README documentation with details on non-kms application connectivity to agent dashboards and services, featuring gRPC access protocols via the zt-https proxy gateway.