-
Notifications
You must be signed in to change notification settings - Fork 120
Register Radius.Compute and Radius.Security resource types by default #11062
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
base: main
Are you sure you want to change the base?
Conversation
…`Radius.Security/secrets` resource types automatically on Radius installation. These types are defined in [resource-types-contrib](https://github.com/radius-project/resource-types-contrib) and previously required manual registration. Signed-off-by: Karishma Chawla <kachawla@microsoft.com>
Update manifest file naming convention to use underscores instead of hyphens for consistency with other provider manifest files. Signed-off-by: Karishma Chawla <kachawla@microsoft.com>
…source types Updated the test to use API version 2025-08-01-preview for all Radius.* resource types (not just Radius.Core). This is needed because the newly added Radius.Compute and Radius.Security resource types also use the 2025-08-01-preview API version. Signed-off-by: Karishma Chawla <kachawla@microsoft.com>
cfc49e1 to
7dc2f48
Compare
Radius functional test overviewClick here to see the test run details
Test Status⌛ Building Radius and pushing container images for functional tests... |
| location: | ||
| global: "http://localhost:8082" |
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.
Can you explain why we added location? Location is an unused and unnecessary property on our existing resource types. We specifically did not want to include them in the new resource types.
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.
This is routing location. I'm guessing your comment is assuming this is a part of the schema (it is not)?
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.
I see. Yes, my comment was about the location property in the schema.
Description
Register
Radius.Compute/{containers,routes,persistentVolumes}andRadius.Security/secretsresource types automatically on Radius installation. These types are defined in resource-types-contrib and previously required manual registration.Changes
Added manifest files for both dev and self-hosted environments:
deploy/manifest/built-in-providers/{dev,self-hosted}/radius_compute.yaml- defines containers, routes, persistentVolumes types with complete OpenAPI schemasdeploy/manifest/built-in-providers/{dev,self-hosted}/radius_security.yaml- defines secrets type with complete OpenAPI schemaThe manifests include the full schema definitions from resource-types-contrib. The only difference from the upstream definitions is the addition of a
locationfield, which specifies where the resource provider is hosted (required for Radius deployment).Manifests are included in UCP image via
deploy/images/ucpd/Dockerfileand loaded automatically by the initializer service during startup. Resource types route todynamic-rpservice (http://dynamic-rp.radius-system:8082for self-hosted,http://localhost:8082for dev).Type of change
Partially Fixes: #9830
Contributor checklist
Please verify that the PR meets the following requirements, where applicable: