Add an end-to-end sample tutorial for local, Azure, and AWS deployment

Abierto
  • ¿Algo no está bien?
#2,079 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
aws, azure, kubernetes
Área
cloud, documentation

Línea de trabajo

Start with the cloud guides and relevant how-to pages, then review #1701, #2078, #2042, and existing Radius samples or labs for reusable material. Define a repeatable validation procedure for one application across local Kubernetes, Azure, and AWS; done means the tutorial links to a tested sample revision and covers setup, functional verification, differences, costs, troubleshooting, and cleanup.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What content needs to be created or modified?

Provide one canonical sample and a step-by-step tutorial that connects application modeling, Resource Types, connections, Environments, Recipe Packs, and deployment. Readers should be able to follow the same application from local development to Azure and AWS, rather than assembling a workflow from isolated how-to pages.

This is a concrete, bounded follow-up to #1701. Reuse an existing sample or lab where practical, and update any reused material to current Radius resource types and commands.

Describe the solution you'd like

Choose one small but representative application with a container workload and a backing service, such as a database. Publish the runnable source and deployment artifacts in a canonical location, and write a tutorial that:

  1. Introduces the application, its dependencies, and the intended deployment in each Environment.
  2. Shows how to model or adapt it for Radius, including resource definitions and connections.
  3. Deploys and verifies it on a local Kubernetes cluster.
  4. Configures credentials, an Environment, and Recipe Packs for Azure, then deploys and verifies the same application.
  5. Repeats the cloud deployment for AWS, explaining which configuration changes and which application definitions remain unchanged.
  6. Removes sample resources and explains any retained resources or data and potential costs.

Use the cloud-specific guidance tracked in #2078 for detailed credentials and module setup. Keep shared application source and application definitions in one place; isolate cloud-specific configuration in the appropriate Environment and recipe artifacts. Explain any unavoidable differences rather than claiming unrestricted portability.

Acceptance criteria
  • One documented sample runs locally, on Azure, and on AWS with stated Radius and dependency versions.
  • The tutorial includes complete prerequisites, commands, expected results, and links to the source files used at each step.
  • The sample uses current Radius.* resource types rather than legacy Applications.* examples.
  • Each target has a functional verification step that exercises the application and its backing service, not just successful resource creation or healthy pods.
  • Readers can see which artifacts are shared and which differ by deployment target; limitations and cloud-specific behavior are documented.
  • Cloud permissions, networking requirements, cost considerations, troubleshooting, and cleanup are covered.
  • A repeatable validation procedure and maintenance location are documented, with automated checks where practical.
  • The tutorial is discoverable from the cloud guides without expanding the basic Getting Started quickstart into an advanced cloud tutorial.

Where should the new material be placed?

In a dedicated tutorials area linked from AWS and Azure and the relevant how-to guides. Reuse or modernize existing labs where appropriate. Keep runnable source in a canonical sample location, such as the Radius samples repository, and link to a tested revision rather than copying diverging versions into multiple pages.

The associated pull request from the Radius code repo, if applicable

N/A. Link any sample-repository implementation PRs here when available.

Additional context

Related work:

  • #1701: broader scenario-based tutorials and reference architectures.
  • #2078: dedicated AWS and Azure setup and module guidance.
  • #2042: cloud support visibility and navigation.

Scope is one reproducible application across three targets, not a rewrite of the entire samples repository. Deploying the same application to separate Environments is not a data migration, cross-cloud failover, or production-readiness guarantee.

Lenguaje dominante
Bicep
Estrellas
27
Forks
51
Merge medio
1 d 8 h
PR fusionados (30 d)
37

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de radius-project/docs

Todos los issues de radius-project/docs

Issues similares

Más issues de Cloud

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.