feat(gateway): support multi-port serving in deploy scripts #490
+17
−4
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.
Summary
GATEWAY_SERVING_ADDRwithGATEWAY_SERVING_PORT+GATEWAY_SERVING_NUM_PORTSin deploy scriptlisten_port = "443-462"style config whenSERVING_NUM_PORTS > 1SERVING_NUM_PORTS=1preserves full backwards compatibilityContext
Follow-up to #489 (multi-port TCP listening). The gateway binary now supports port ranges, but the deploy scripts still mapped a single serving port. This PR makes the deploy tooling aware of multi-port configuration.
Configuration
In
.env:Test Results
SERVING_NUM_PORTS=3generateslisten_port = "443-445"in container configlisten_port = 443(backwards compatible)cr.kvin.wang/dstack-gateway:multi-portimage