radius-project / radius-project/roadmap
Compute platform extensibility
Open
@willtsai is already working on this.
Since Jan 29, 2026.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Overview of roadmap item
Radius will provide extensible support for multiple compute platforms through recipes rather than hard-coded support for each platform.
Core resource types (containers, gateways, and secretStores) will allow recipes to be registered for them, with default recipes for Kubernetes and Azure Container Instances (ACI) provided by Radius. Customers can use, modify, or remove the default recipes.
This design should enable:
- Architectural separation of Radius core logic from platform provisioning code
- Community-provided extensions to support new compute platforms without Radius code changes
- Consistent platform engineering experience across all resource types
Related issues
#53
#54
Additional context
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.