Skip to content

Conversation

@kachawla
Copy link
Contributor

@kachawla kachawla commented Jan 23, 2026

Description

Register Radius.Compute/{containers,routes,persistentVolumes} and Radius.Security/secrets resource 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 schemas
  • deploy/manifest/built-in-providers/{dev,self-hosted}/radius_security.yaml - defines secrets type with complete OpenAPI schema

The manifests include the full schema definitions from resource-types-contrib. The only difference from the upstream definitions is the addition of a location field, which specifies where the resource provider is hosted (required for Radius deployment).

Manifests are included in UCP image via deploy/images/ucpd/Dockerfile and loaded automatically by the initializer service during startup. Resource types route to dynamic-rp service (http://dynamic-rp.radius-system:8082 for self-hosted, http://localhost:8082 for dev).

Type of change

  • This pull request fixes a bug in Radius and has an approved issue (issue link required).
  • This pull request adds or changes features of Radius and has an approved issue (issue link required).
  • This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and doesn't change the functionality of Radius (issue link optional).

Partially Fixes: #9830

Contributor checklist

Please verify that the PR meets the following requirements, where applicable:

  • An overview of proposed schema changes is included in a linked GitHub issue.
    • Yes
    • Not applicable
  • A design document PR is created in the design-notes repository, if new APIs are being introduced.
    • Yes
    • Not applicable
  • The design document has been reviewed and approved by Radius maintainers/approvers.
    • Yes
    • Not applicable
  • A PR for the samples repository is created, if existing samples are affected by the changes in this PR.
    • Yes
    • Not applicable
  • A PR for the documentation repository is created, if the changes in this PR affect the documentation or any user facing updates are made.
    • Yes
    • Not applicable
  • A PR for the recipes repository is created, if existing recipes are affected by the changes in this PR.
    • Yes
    • Not applicable

…`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>
@kachawla kachawla requested review from a team as code owners January 23, 2026 01:44
@kachawla kachawla temporarily deployed to functional-tests January 23, 2026 01:44 — with GitHub Actions Inactive
@kachawla kachawla requested a review from lakshmimsft January 23, 2026 01:45
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>
@radius-functional-tests
Copy link

radius-functional-tests bot commented Jan 23, 2026

Radius functional test overview

🔍 Go to test action run

Click here to see the test run details
Name Value
Repository kachawla/radius
Commit ref 7dc2f48
Unique ID func3c90a15fe7
Image tag pr-func3c90a15fe7
  • gotestsum 1.13.0
  • KinD: v0.29.0
  • Dapr: 1.14.4
  • Azure KeyVault CSI driver: 1.4.2
  • Azure Workload identity webhook: 1.3.0
  • Bicep recipe location ghcr.io/radius-project/dev/test/testrecipes/test-bicep-recipes/<name>:pr-func3c90a15fe7
  • Terraform recipe location http://tf-module-server.radius-test-tf-module-server.svc.cluster.local/<name>.zip (in cluster)
  • applications-rp test image location: ghcr.io/radius-project/dev/applications-rp:pr-func3c90a15fe7
  • dynamic-rp test image location: ghcr.io/radius-project/dev/dynamic-rp:pr-func3c90a15fe7
  • controller test image location: ghcr.io/radius-project/dev/controller:pr-func3c90a15fe7
  • ucp test image location: ghcr.io/radius-project/dev/ucpd:pr-func3c90a15fe7
  • deployment-engine test image location: ghcr.io/radius-project/deployment-engine:latest

Test Status

⌛ Building Radius and pushing container images for functional tests...
✅ Container images build succeeded
⌛ Publishing Bicep Recipes for functional tests...
✅ corerp-cloud functional tests succeeded
✅ Recipe publishing succeeded
⌛ Starting corerp-cloud functional tests...
⌛ Starting ucp-cloud functional tests...
✅ ucp-cloud functional tests succeeded
✅ corerp-cloud functional tests succeeded

Comment on lines +2 to +3
location:
global: "http://localhost:8082"
Copy link
Contributor

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.

Copy link
Contributor Author

@kachawla kachawla Jan 26, 2026

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)?

Copy link
Contributor

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.

@kachawla kachawla requested review from nicolejms and nithyatsu and removed request for nicolejms January 26, 2026 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Compute Extensibility] Integrate new core RRTs into Radius

2 participants