feat(routing): Add regional scheduling and Node TLS - #185
Merged
Conversation
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
1 participant
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
Deployments can select a region and are placed on healthy Serve nodes using CPU, memory, disk, and deployment-slot capacity. Nodes retain the complete Host route snapshot and deliver sites through at most one peer hop.
This branch also contributes native Node TLS, certificate hot reload, and a regional entry failover test. Its original commits are preserved in #184, which integrates the complementary Control API, Console, gateway, and DNS provider changes. Merge this work into
developthrough #184 so the final tree includes the complete integration and its subsequent fixes.Validation
just qualityand integration CI passed in feat(platform): Add regional delivery and managed HTTPS #184. This older branch's standalone audit found the h2 0.4.15 advisory; the integrated tree includes h2 0.4.16 and passes the audit.Tracking
Closes #180
Related: #181
Parent: #179
Integrated through #184. Closing references must be repeated when promoting
developtomain.Known Limitations
Entry failover assumes that the deployment's assigned Serve node remains healthy. Automatic deployment relocation is separate work.