Support additional cloud providers

Overview

Expand Radius Canvas deployment beyond Azure while preserving a consistent experience for modeling Applications, configuring Environments, planning infrastructure, deploying resources, monitoring progress, troubleshooting failures, and deleting deployments.

Each provider integration should support provider-specific authentication, infrastructure discovery, Radius Environment configuration, resource types, recipes, and GitHub Actions workflows. Provider-specific behavior should not require developers to restructure the core Radius application definition.

Radius Canvas should show how application requirements map to infrastructure on the selected provider. The Planned and Deployed views should display the provider resources created for the Application and link them back to their corresponding Radius resources.

Expected outcomes

• Configure Radius Environments for additional cloud providers.
• Authenticate GitHub Actions using provider-supported workload identity.
• Discover supported accounts, regions, clusters, and deployment targets.
• Resolve Radius resources through provider-specific recipes.
• Preview the infrastructure planned for the selected provider.
• Deploy Applications and infrastructure through GitHub Actions.
• Display provider-specific deployment status and errors.
• Support deployment deletion and credential cleanup.
• Document provider-specific prerequisites and limitations.
• Preserve a consistent Application model across providers.

Additional context

The current preview deploys Applications to Azure. Additional providers should build on the shared modeling, platform, graph, and workflow-generation logic in radius-project/ai-extensions.

Start by reviewing the current Azure preview and the shared modeling, platform, graph, and workflow-generation logic in radius-project/ai-extensions. Define the additional provider scope with maintainers, then verify that the selected provider supports the listed authentication, discovery, planning, deployment, monitoring, deletion, and documentation outcomes without changing the core Application model.