-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[UDT PR 7 / N] Implement routing for UDT #8070
Conversation
For reviewers: this is the best place to start reviewing. This is the core logic we use to route requests. Every other change in this PR is either glue-code or a test update 😆 |
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A question and a nit :)
@nithyatsu @ytimocin @lakshmimsft - updated and resolved feedback. |
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
This change adds support routing decisions based on UDT registrations. The logic in UCP that deals with request routing will now check for resource types and resource provider locations, with a fallback to the previous logic for compatibility. This is powered by a new configuration setting in UCP's configuration, that will be configured to the URL of dynamic-rp. Note that there's nothing in dynamic-rp yet to serve these requests. This will be done in a follow-up. Signed-off-by: Ryan Nowak <nowakra@gmail.com>
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Description
This change adds support routing decisions based on UDT registrations. The logic in UCP that deals with request routing will now check for resource types and resource provider locations, with a fallback to the previous logic for compatibility.
This is powered by a new configuration setting in UCP's configuration, that will be configured to the URL of dynamic-rp.
Note that there's nothing in dynamic-rp yet to serve these requests. This will be done in a follow-up.
Type of change
Part of: #6688
Contributor checklist
Please verify that the PR meets the following requirements, where applicable: