Container recipe design for RRT

[brooke-hamilton]

Migrate Container Resource Deployment to Bicep

This PR migrates container resource deployment from Go-based renderer chains (Applications.Core/containers) to a declarative Bicep recipe for Radius.Compute/containers. The approach uses the Bicep Kubernetes extension (preview) to generate native Kubernetes resources, supporting multi-container setups, volumes, identity, RBAC, connections, and all core extensions (Dapr sidecars, manual scaling, metadata).

Highlights:

• Declarative Bicep replaces imperative Go logic for container resources.
• Full support for new Radius.Compute/containers schema.
• Extension logic (Dapr, scaling, metadata) replicated in Bicep.
• VS Code integration and IntelliSense for resource authoring.
• Legacy renderer chain remains for existing resources; new deployments use recipes.

[nithyatsu]

This might be OK, since we do have RRT2RRT connections support, which does the same environment variable processing for sources that are resource ids .

[ytimocin]

Can you explain how migrating container resource deployment from Go-based renderer chains (Applications.Core/containers) to a declarative Bicep recipe for Radius.Compute/containers help Radius? I am trying to understand the main goal here.

[brooke-hamilton]

Can you explain how migrating container resource deployment from Go-based renderer chains (Applications.Core/containers) to a declarative Bicep recipe for Radius.Compute/containers help Radius? I am trying to understand the main goal here.

Another way of saying this is that we are moving all the kubernetes deployment logic that is currently in Go over to a Bicep recipe (and a Terraform recipe.)

[Copilot]

Pull Request Overview

This PR introduces a container recipe design document for migrating Radius container resource deployment from imperative Go renderer chains to declarative Bicep recipes. The migration targets the new Radius.Compute/containers resource type and leverages the Bicep Kubernetes extension for native Kubernetes resource generation.

Key changes:

• Container resource migration strategy: Comprehensive design for replacing Applications.Core/containers Go renderers with Bicep recipes for Radius.Compute/containers
• Bicep Kubernetes extension integration: Detailed approach using the preview extension for direct Kubernetes resource creation with type safety and VS Code support
• Feature parity analysis: Complete mapping of current renderer chain functionality (multi-container support, extensions, volumes, identity, RBAC) to recipe-based implementation

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
recipe/2025-09-container.md	Design document outlining the migration from Go renderer chains to Bicep recipes for container resources
.github/config/en-custom.txt	Added custom dictionary terms related to Kubernetes and container concepts used in the design document

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}