Add managed Gateway lifecycle for routes - #12854
Closed
willdavsmith wants to merge 4 commits into
Closed
Conversation
Copilot-Session: 8ef3ad83-8b46-4c4c-8a5c-405c2f476616 Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Copilot-Session: 90bbcc1b-c1e4-49f6-ac53-261516d66bda Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Copilot-Session: 90bbcc1b-c1e4-49f6-ac53-261516d66bda Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Copilot-Session: 90bbcc1b-c1e4-49f6-ac53-261516d66bda Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Radius functional test overviewClick here to see the test run details
Test Status⌛ Building Radius and pushing container images for functional tests... |
Contributor
Author
|
Superseded by radius-project/ai-extensions#672 after the Repo Radius extension workflows and actions moved to ai-extensions. |
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
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
Add an idempotent, provider-neutral Gateway API lifecycle for repo-driven
Radius.Compute/routesdeployments. Azure and AWS workflows now detect when the Radius default routes recipe needs shared infrastructure, validate BYO Gateways without adopting them, and otherwise reconcile pinned Contour and Gateway API resources with privateClusterIPexposure by default.Cleanup runs after successful application deletion, fails closed on discovery uncertainty, and preserves the managed stack while Radius routes or non-Radius Gateway API, Ingress, or Contour consumers remain. Deploy and delete workflows serialize per repository and Radius environment to avoid ensure/deploy/delete races.
Reason for change
Repo Radius deploy workflows must support
Radius.Compute/routeswithout creating a public IP by default while safely sharing target-cluster Gateway infrastructure.Fixes radius-project/ai-extensions#421.
Companion documentation: radius-project/ai-extensions#570.
How to test
File change summary
.github/extension/actions/manage-routes-gateway/action.yml.github/extension/actions/manage-routes-gateway/routes-gateway.sh.github/extension/actions/manage-routes-gateway/routes-gateway_test.sh.github/extension/run-rad-commands-azure.yml.github/extension/run-rad-commands-aws.yml.github/extension/delete-azure.yml.github/extension/delete-aws.yml.github/extension/README.mdbuild/test.mk