diff --git a/.github/config/en-custom.txt b/.github/config/en-custom.txt index 53eff00f9..c99f0f5d3 100644 --- a/.github/config/en-custom.txt +++ b/.github/config/en-custom.txt @@ -946,4 +946,6 @@ XRay PodSpec ConfigMap CRD -composable \ No newline at end of file +composable +gatewaydemo +tlsdemo \ No newline at end of file diff --git a/docs/content/concepts/api-concept/index.md b/docs/content/concepts/api-concept/index.md index b2f34006a..27a43f918 100644 --- a/docs/content/concepts/api-concept/index.md +++ b/docs/content/concepts/api-concept/index.md @@ -84,7 +84,7 @@ The following tables shows some examples of resource ids from different resource #### Resource manager: Radius -This example shows a Radius application named `my-app` in the `my-group` resource group, running on the local cluster: +This example shows a Radius Application named `my-app` in the `my-group` resource group, running on the local cluster: | Key | Example | | ------------------ | ------------------------------------------------------------------------------------ | diff --git a/docs/content/concepts/application-graph/index.md b/docs/content/concepts/application-graph/index.md index f608df33f..de2db4288 100644 --- a/docs/content/concepts/application-graph/index.md +++ b/docs/content/concepts/application-graph/index.md @@ -7,21 +7,21 @@ weight: 200 toc_hide: true --- -## Radius applications +## Radius Applications -Radius offers an [application resource]({{< ref "guides/author-apps/application" >}}) which teams can use to define and deploy their entire application, including all of the compute, relationships, and infrastructure that make up the application. Since the graph of relationships between deployed resources is much more descriptive than a basic list of resources, the Radius application graph can automate complex deployment tasks and enable rich visualization experiences. +Radius offers an [application resource]({{< ref "guides/author-apps/application" >}}) which teams can use to define and deploy their entire application, including all of the compute, relationships, and infrastructure that make up the application. Since the graph of relationships between deployed resources is much more descriptive than a basic list of resources, the Radius Application graph can automate complex deployment tasks and enable rich visualization experiences. A diagram showing an application and all it's resources ## Graphs are better than lists -Within an application deployed with Radius, developers can express both the resources (_containers, databases, message queues, etc._), as well as all the relationships between them. This forms the Radius application graph. This graph is powerful because it allows Radius to understand the relationships between resources, simplifying the [deployment]({{< ref "/guides/deploy-apps" >}}) and [configuration]({{< ref "application" >}}) of your application. Plus, it allows you to visualize your application in a way that is more intuitive than a list of resources. +Within an application deployed with Radius, developers can express both the resources (_containers, databases, message queues, etc._), as well as all the relationships between them. This forms the Radius Application graph. This graph is powerful because it allows Radius to understand the relationships between resources, simplifying the [deployment]({{< ref "/guides/deploy-apps" >}}) and [configuration]({{< ref "application" >}}) of your application. Plus, it allows you to visualize your application in a way that is more intuitive than a list of resources. A diagram showing the move from a set of infrastructure lists to a graph of resources ## Self-documenting applications -The Radius application graph also allows your application to be self-documenting, where developers and operators can query and reason about the same application definition. Instead of multiple views of logs, infrastructure, and code, Radius provides a single source of truth for your application. +The Radius Application graph also allows your application to be self-documenting, where developers and operators can query and reason about the same application definition. Instead of multiple views of logs, infrastructure, and code, Radius provides a single source of truth for your application. A mockup of a dashboard UI showing an application, its resources, and its connections @@ -29,7 +29,7 @@ The Radius application graph also allows your application to be self-documenting ## Mine the app graph API -The Radius application graph is also exposed as an API, allowing you to build your own visualizations, workflows, and more on top of Radius. Learn more in the [API docs]({{< ref api-concept >}}). +The Radius Application graph is also exposed as an API, allowing you to build your own visualizations, workflows, and more on top of Radius. Learn more in the [API docs]({{< ref api-concept >}}). For example, I can get the status of my `frontend` container, and get its definition and its connections to other resources: diff --git a/docs/content/concepts/architecture-concept/index.md b/docs/content/concepts/architecture-concept/index.md index 9ba1cbfff..8ca6be452 100644 --- a/docs/content/concepts/architecture-concept/index.md +++ b/docs/content/concepts/architecture-concept/index.md @@ -139,7 +139,7 @@ When listing applications using the `rad` CLI: {{% /codetab %}} {{% codetab %}} -When using Bicep to author and deploy Radius applications: +When using Bicep to author and deploy Radius Applications: 1. The client compiles the Bicep file to an ARM-JSON template and submits a request for processing as a `Bicep.Deployments/deployments` resource. 2. UCP receives the request for the `Bicep.Deployments/deployments` Create operation and looks up the internal address for the `Bicep.Deployments` resource provider. @@ -153,7 +153,7 @@ When using Bicep to author and deploy Radius applications: {{% /codetab %}} {{% codetab %}} -When using the `tf` CLI to deploy a Radius application using Terraform: +When using the `tf` CLI to deploy a Radius Application using Terraform: 1. Terraform reads the configuration, loads credentials, parses the file, and instantiates its providers. For each resource in the file: a. Terraform asks the appropriate provider to Create or Update the resource. diff --git a/docs/content/concepts/environments-concept/index.md b/docs/content/concepts/environments-concept/index.md index 4fb0daee9..751d57910 100644 --- a/docs/content/concepts/environments-concept/index.md +++ b/docs/content/concepts/environments-concept/index.md @@ -1,6 +1,6 @@ --- type: docs -title: "Radius environments" +title: "Radius Environments" linkTitle: "Environments" description: "Learn about Radius Environments" weight: 300 @@ -10,23 +10,23 @@ toc_hide: true ## Introduction -Radius environments are a prepared landing zone for applications. They contain a prepared pool of compute, networking, and shared resources. Radius applications deployed to that environment "bind" to that infrastructure. Configuration on the environment allow for operators to enforce organizational requirements and best practices for app teams. +Radius Environments are a prepared landing zone for applications. They contain a prepared pool of compute, networking, and shared resources. s deployed to that environment "bind" to that infrastructure. Configuration on the environment allow for operators to enforce organizational requirements and best practices for app teams. -Environments provide a grouping structure for applications and the resources they share. For example, an org might choose to setup separate Radius environments for staging and production. When appropriate, multiple applications can be deployed into the same environment. +Environments provide a grouping structure for applications and the resources they share. For example, an org might choose to setup separate Radius Environments for staging and production. When appropriate, multiple applications can be deployed into the same environment. -Diagram of multiple Radius environments deployed to Azure. One environment contains 1 app, the other environment contains multiple apps. +Diagram of multiple Radius Environments deployed to Azure. One environment contains 1 app, the other environment contains multiple apps. ## Concerns that environments manage ### Separation of concerns -In many small to medium-sized organizations, a full stack developer might write application code, author the Radius app definition, and create the Radius environment. In larger orgs, there may be separate teams of central operations and developers, where the central teams build environment templates which development teams leverage and deploy to. The separation of an app from an environment makes a separation of concerns possible. +In many small to medium-sized organizations, a full stack developer might write application code, author the Radius app definition, and create the Radius Environment. In larger orgs, there may be separate teams of central operations and developers, where the central teams build environment templates which development teams leverage and deploy to. The separation of an app from an environment makes a separation of concerns possible. -With Radius environments, central operations and IT teams can define and share environments with development teams for them to deploy applications into. Ops teams can focus on configuring the compute, dependencies, networking, and other infrastructure concerns through [Recipes]({{< ref "guides/recipes/overview">}}), while developers focus on the business and application concerns. This allows each team to focus on what matters most to them, without needing to become experts in every aspect of the infrastructure and application. +With Radius Environments, central operations and IT teams can define and share environments with development teams for them to deploy applications into. Ops teams can focus on configuring the compute, dependencies, networking, and other infrastructure concerns through [Recipes]({{< ref "guides/recipes/overview">}}), while developers focus on the business and application concerns. This allows each team to focus on what matters most to them, without needing to become experts in every aspect of the infrastructure and application. ### Developer productivity -Once an environment template is defined, developers can get up and running with a prepared development, pre-production, or production environment in minutes. No more waiting for manual provisioning, configuration or inter-team coordination. Simply use the [Recipes]({{< ref "guides/recipes/overview" >}}) linked to your Radius environment and deploy your application. +Once an environment template is defined, developers can get up and running with a prepared development, pre-production, or production environment in minutes. No more waiting for manual provisioning, configuration or inter-team coordination. Simply use the [Recipes]({{< ref "guides/recipes/overview" >}}) linked to your Radius Environment and deploy your application. ### Replication and consistency @@ -34,7 +34,7 @@ When an application team needs to scale an application to additional regions or ### Organization best-practices -Organizational best-practices such as cost-optimization, resource sharing, and logging can all be codified and enforced with a Radius environment. +Organizational best-practices such as cost-optimization, resource sharing, and logging can all be codified and enforced with a Radius Environment. ## Environment features @@ -56,8 +56,8 @@ In this example there are two teams within an organization: a central operations A typical workflow for this team structure would look like: 1. The ops team initializes a new environment, configured with a compute runtime setup with networking, identity, diagnostics, and other configuration that matches their org's requirements. -1. The developer authors a Radius application template, including containers for their services, portable resources for their infrastructure, and routes/gateways for their networking. -1. The developer deploys the app template to the Radius environment +1. The developer authors a Radius Application template, including containers for their services, portable resources for their infrastructure, and routes/gateways for their networking. +1. The developer deploys the app template to the Radius Environment - The app's containers automatically run on the container runtime - The resource automatically configures security best practices and injects connection information into the consuming container diff --git a/docs/content/concepts/overview/index.md b/docs/content/concepts/overview/index.md index caa134eb9..9c0c62a7c 100644 --- a/docs/content/concepts/overview/index.md +++ b/docs/content/concepts/overview/index.md @@ -36,13 +36,13 @@ These new resources form the [**Radius app model**]({{< ref application-graph>}} The result is no longer just a flat list of resources - it's a fully codified abstraction of how the services and infrastructure relate to each other: -Diagram showing Radius application in the Azure portal
+Diagram showing Radius Application in the Azure portal
### Drastically reduce infra ops time [App environments]({{< ref environments-concept >}}) are landing zones for applications. They are the place where you can deploy, manage, and scale your apps. -Diagram showing Radius environments +Diagram showing Radius Environments Environments allow you to: @@ -88,4 +88,4 @@ As teams onboard to Radius and begin deploying across platforms, the tooling and Now that you have an overview of Radius, learn more about the Radius app model: -{{< button text="Learn about the Radius application model" page="application-graph" size="btn-lg" color="success" >}} \ No newline at end of file +{{< button text="Learn about the Radius Application model" page="application-graph" size="btn-lg" color="success" >}} \ No newline at end of file diff --git a/docs/content/getting-started/index.md b/docs/content/getting-started/index.md index df61e6e65..5a2a5cb44 100644 --- a/docs/content/getting-started/index.md +++ b/docs/content/getting-started/index.md @@ -137,7 +137,7 @@ Press CTRL+ C when you are finished with the website. ## 7. View the application connections -Radius connections are more than just environment variables and configuration. You can also access the "application graph" and understand the connections within your application with the following command: +Radius Connections are more than just environment variables and configuration. You can also access the "application graph" and understand the connections within your application with the following command: ```bash rad app connections diff --git a/docs/content/getting-started/snippets/app-with-redis-snippets.bicep b/docs/content/getting-started/snippets/app-with-redis-snippets.bicep index b6625368c..10a2dd5fb 100644 --- a/docs/content/getting-started/snippets/app-with-redis-snippets.bicep +++ b/docs/content/getting-started/snippets/app-with-redis-snippets.bicep @@ -1,7 +1,7 @@ // Import the set of Radius resources (Applications.*) into Bicep import radius as radius -@description('The app ID of your Radius application. Set automatically by the rad CLI.') +@description('The app ID of your Radius Application. Set automatically by the rad CLI.') param application string //CONNECTION @@ -27,7 +27,7 @@ resource demo 'Applications.Core/containers@2023-10-01-preview' = { //CONNECTION //REDIS -@description('The environment ID of your Radius application. Set automatically by the rad CLI.') +@description('The environment ID of your Radius Application. Set automatically by the rad CLI.') param environment string resource db 'Applications.Datastores/redisCaches@2023-10-01-preview' = { diff --git a/docs/content/getting-started/snippets/app-with-redis.bicep b/docs/content/getting-started/snippets/app-with-redis.bicep index 0fdf3f8d2..52704f0f0 100644 --- a/docs/content/getting-started/snippets/app-with-redis.bicep +++ b/docs/content/getting-started/snippets/app-with-redis.bicep @@ -1,7 +1,7 @@ // Import the set of Radius resources (Applications.*) into Bicep import radius as radius -@description('The app ID of your Radius application. Set automatically by the rad CLI.') +@description('The app ID of your Radius Application. Set automatically by the rad CLI.') param application string resource demo 'Applications.Core/containers@2023-10-01-preview' = { diff --git a/docs/content/getting-started/snippets/app.bicep b/docs/content/getting-started/snippets/app.bicep index 95cd46417..9d95b8ba9 100644 --- a/docs/content/getting-started/snippets/app.bicep +++ b/docs/content/getting-started/snippets/app.bicep @@ -1,7 +1,7 @@ // Import the set of Radius resources (Applications.*) into Bicep import radius as radius -@description('The app ID of your Radius application. Set automatically by the rad CLI.') +@description('The app ID of your Radius Application. Set automatically by the rad CLI.') param application string resource demo 'Applications.Core/containers@2023-10-01-preview' = { diff --git a/docs/content/guides/author-apps/_index.md b/docs/content/guides/author-apps/_index.md index 1a98f9892..e5bc51a70 100644 --- a/docs/content/guides/author-apps/_index.md +++ b/docs/content/guides/author-apps/_index.md @@ -2,6 +2,6 @@ type: docs title: "Authoring applications" linkTitle: "Authoring applications" -description: "Learn how to author a Radius application" +description: "Learn how to author a Radius Application" weight: 100 --- \ No newline at end of file diff --git a/docs/content/guides/author-apps/application/_index.md b/docs/content/guides/author-apps/application/_index.md index eb1f60cb3..66c8d4010 100644 --- a/docs/content/guides/author-apps/application/_index.md +++ b/docs/content/guides/author-apps/application/_index.md @@ -1,7 +1,7 @@ --- type: docs -title: "Radius applications" +title: "Radius Applications" linkTitle: "Applications" -description: "Learn about Radius applications" +description: "Learn about Radius Applications" weight: 100 --- \ No newline at end of file diff --git a/docs/content/guides/author-apps/application/overview/index.md b/docs/content/guides/author-apps/application/overview/index.md index f3cc83663..a7923c4cb 100644 --- a/docs/content/guides/author-apps/application/overview/index.md +++ b/docs/content/guides/author-apps/application/overview/index.md @@ -1,8 +1,8 @@ --- type: docs -title: "Overview: Radius applications" +title: "Overview: Radius Applications" linkTitle: "Overview" -description: "Learn about Radius applications and how they bring all of your services, dependencies, and relationships together." +description: "Learn about Radius Applications and how they bring all of your services, dependencies, and relationships together." weight: 100 categories: "Overview" tags: ["applications"] @@ -10,11 +10,11 @@ tags: ["applications"] Diagram of an application -A Radius application is the primary resource that brings all your "stuff" together. This can include services, dependencies, and relationships. Radius apps give you a single description and view into your entire application, and allow you to deploy and manage it easily. +A Radius Application is the primary resource that brings all your "stuff" together. This can include services, dependencies, and relationships. Radius apps give you a single description and view into your entire application, and allow you to deploy and manage it easily. ## Add portability to your application -Radius applications are designed to be cloud and platform agnostic. This means that you can define your application once, and deploy it to any cloud or platform that Radius supports. This allows you to easily move your application between clouds, or even between cloud and on-premises environments. Developers can define their requirements and dependencies (_Redis, SQL, Dapr, etc._) and operators can define the [environments]({{< ref "guides/deploy-apps/environments/overview" >}}) and [Recipes]({{< ref "guides/recipes/overview" >}}) that bind those requirements to the appropriate cloud resources. +Radius Applications are designed to be cloud and platform agnostic. This means that you can define your application once, and deploy it to any cloud or platform that Radius supports. This allows you to easily move your application between clouds, or even between cloud and on-premises environments. Developers can define their requirements and dependencies (_Redis, SQL, Dapr, etc._) and operators can define the [environments]({{< ref "guides/deploy-apps/environments/overview" >}}) and [Recipes]({{< ref "guides/recipes/overview" >}}) that bind those requirements to the appropriate cloud resources. Diagram of portable resources binding to different clouds @@ -30,11 +30,11 @@ The Kubernetes namespace extension allows you to customize how all of the resour ### Kubernetes Metadata extension -The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubernetes-metadata">}}) enables you set and cascade Kubernetes metadata such as labels and Annotations on all the Kubernetes resources defined with in your Radius application. +The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubernetes-metadata">}}) enables you set and cascade Kubernetes metadata such as labels and Annotations on all the Kubernetes resources defined with in your Radius Application. ## Query and understand your application with the Radius Application Graph -Radius applications are more than just client-side configuration and automation, they also provide a server-side graph of your application. This graph can be queried and used to understand your application, and can be used to power other Radius features and custom tooling. Refer to the [API concept docs]({{< ref "api-concept" >}}) and [Postman How-To guide]({{< ref "guides/operations/control-plane/howto-postman" >}}) for more information on how to query the application graph. +Radius Applications are more than just client-side configuration and automation, they also provide a server-side graph of your application. This graph can be queried and used to understand your application, and can be used to power other Radius features and custom tooling. Refer to the [API concept docs]({{< ref "api-concept" >}}) and [Postman How-To guide]({{< ref "guides/operations/control-plane/howto-postman" >}}) for more information on how to query the application graph. Diagram of the application graph diff --git a/docs/content/guides/author-apps/application/overview/snippets/blank.bicep b/docs/content/guides/author-apps/application/overview/snippets/blank.bicep index d324ea9b9..bd50b2da0 100644 --- a/docs/content/guides/author-apps/application/overview/snippets/blank.bicep +++ b/docs/content/guides/author-apps/application/overview/snippets/blank.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The environment ID of your Radius application. Set automatically by the rad CLI.') +@description('The environment ID of your Radius Application. Set automatically by the rad CLI.') param environment string resource myapp 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/guides/author-apps/aws/howto-aws-resources/index.md b/docs/content/guides/author-apps/aws/howto-aws-resources/index.md index 7e4b93549..78e1f0c00 100644 --- a/docs/content/guides/author-apps/aws/howto-aws-resources/index.md +++ b/docs/content/guides/author-apps/aws/howto-aws-resources/index.md @@ -34,9 +34,9 @@ Create an EKS cluster by using the `eksctl` CLI. eksctl create cluster --name --region= ``` -## Step 2: Create a Radius environment with the AWS cloud provider +## Step 2: Create a Radius Environment with the AWS cloud provider -Create a [Radius environment]({{< ref "/guides/deploy-apps/environments/overview" >}}) where you will deploy your application. +Create a [Radius Environment]({{< ref "/guides/deploy-apps/environments/overview" >}}) where you will deploy your application. Run [`rad init --full`]({{< ref rad_init >}}) to initialize a new environment into your current kubectl context: @@ -98,7 +98,7 @@ This creates a container that will be deployed to your Kubernetes cluster. This 1. When you're done with testing, you can use the rad CLI to [delete an environment]({{< ref rad_env_delete.md >}}) to delete all Radius resources running on the EKS Cluster. -2. Cleanup AWS Resources - AWS resources are not deleted when deleting a Radius environment, so make sure to delete all resources created in this reference app to prevent additional charges. You can delete these resources in the AWS Console or via the AWS CLI. Instructions to delete an AWS S3 Bucket are available [here](https://docs.aws.amazon.com/AmazonS3/latest/userguide/delete-bucket.html). +2. Cleanup AWS Resources - AWS resources are not deleted when deleting a Radius Environment, so make sure to delete all resources created in this reference app to prevent additional charges. You can delete these resources in the AWS Console or via the AWS CLI. Instructions to delete an AWS S3 Bucket are available [here](https://docs.aws.amazon.com/AmazonS3/latest/userguide/delete-bucket.html). ## Troubleshooting diff --git a/docs/content/guides/author-apps/aws/howto-aws-resources/snippets/app.bicep b/docs/content/guides/author-apps/aws/howto-aws-resources/snippets/app.bicep index f298336a1..be351c82c 100644 --- a/docs/content/guides/author-apps/aws/howto-aws-resources/snippets/app.bicep +++ b/docs/content/guides/author-apps/aws/howto-aws-resources/snippets/app.bicep @@ -12,7 +12,7 @@ resource s3 'AWS.S3/Bucket@default' = { } } -@description('The environment ID of your Radius application. Set automatically by the rad CLI.') +@description('The environment ID of your Radius Application. Set automatically by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/guides/author-apps/aws/howto-aws-resources/snippets/s3app.bicep b/docs/content/guides/author-apps/aws/howto-aws-resources/snippets/s3app.bicep index b091624fa..360b11b89 100644 --- a/docs/content/guides/author-apps/aws/howto-aws-resources/snippets/s3app.bicep +++ b/docs/content/guides/author-apps/aws/howto-aws-resources/snippets/s3app.bicep @@ -13,7 +13,7 @@ resource s3 'AWS.S3/Bucket@default' = { } //S3APP -@description('The environment ID of your Radius application. Set automatically by the rad CLI.') +@description('The environment ID of your Radius Application. Set automatically by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/guides/author-apps/aws/overview/index.md b/docs/content/guides/author-apps/aws/overview/index.md index 705f30f3b..a00005157 100644 --- a/docs/content/guides/author-apps/aws/overview/index.md +++ b/docs/content/guides/author-apps/aws/overview/index.md @@ -8,13 +8,13 @@ categories: "Overview" tags: ["AWS"] --- -Radius applications are able to connect to and leverage AWS resource with Bicep. Simply model your AWS resources in Bicep and connect to them from Radius resources. +Radius Applications are able to connect to and leverage AWS resource with Bicep. Simply model your AWS resources in Bicep and connect to them from Radius resources. Radius uses the [AWS Cloud Control API](https://docs.aws.amazon.com/cloudcontrolapi/latest/userguide/what-is-cloudcontrolapi.html) to interact with AWS resources. This means that you can model your AWS resources in Bicep and Radius will be able to deploy and manage them. ## Configure an AWS Provider -The AWS provider allows you to deploy and connect to AWS resources from a Radius environment on an EKS cluster. To configure an AWS provider, you can follow the documentation [here]({{< ref "/guides/operations/providers/howto-aws-provider" >}}). +The AWS provider allows you to deploy and connect to AWS resources from a Radius Environment on an EKS cluster. To configure an AWS provider, you can follow the documentation [here]({{< ref "/guides/operations/providers/howto-aws-provider" >}}). ## Example diff --git a/docs/content/guides/author-apps/azure/howto-azure-resources/index.md b/docs/content/guides/author-apps/azure/howto-azure-resources/index.md index 88ed0e843..7e3b5e11e 100644 --- a/docs/content/guides/author-apps/azure/howto-azure-resources/index.md +++ b/docs/content/guides/author-apps/azure/howto-azure-resources/index.md @@ -11,7 +11,7 @@ tags: ["Azure","containers"] This how-to guide will provide an overview of how to: -- Setup a Radius environment with an identity provider +- Setup a Radius Environment with an identity provider - Define a connection to an Azure resource with Azure AD role-based access control (RBAC) assignments - Leverage Azure managed identities to connect to an Azure resource @@ -31,15 +31,15 @@ Begin by running [`rad init --full`]({{< ref rad_init >}}). Make sure to configu rad init --full ``` -## Step 2: Define a Radius environment +## Step 2: Define a Radius Environment -Create a file named `app.bicep` and define a Radius environment with [identity property]({{< ref "/guides/deploy-apps/environments/overview" >}}) set. This configures your environment to use your Azure AD workload identity installation with your cluster's OIDC endpoint: +Create a file named `app.bicep` and define a Radius Environment with [identity property]({{< ref "/guides/deploy-apps/environments/overview" >}}) set. This configures your environment to use your Azure AD workload identity installation with your cluster's OIDC endpoint: {{< rad file="snippets/container-wi.bicep" embed=true marker="//ENVIRONMENT">}} ## Step 3: Define an app and a container -Add a Radius application, a Radius [container]({{< ref "guides/author-apps/containers" >}}), and an Azure Key Vault to your `app.bicep` file. Note the connection from the container to the Key Vault, with an iam property set for the Azure AD RBAC role: +Add a Radius Application, a Radius [container]({{< ref "guides/author-apps/containers" >}}), and an Azure Key Vault to your `app.bicep` file. Note the connection from the container to the Key Vault, with an iam property set for the Azure AD RBAC role: {{< rad file="snippets/container-wi.bicep" embed=true marker="//CONTAINER" >}} diff --git a/docs/content/guides/author-apps/azure/overview/index.md b/docs/content/guides/author-apps/azure/overview/index.md index 90aeb3100..1c944603b 100644 --- a/docs/content/guides/author-apps/azure/overview/index.md +++ b/docs/content/guides/author-apps/azure/overview/index.md @@ -8,11 +8,11 @@ categories: "Overview" tags: ["Azure"] --- -Radius applications are able to connect to and leverage every Azure resource with Bicep. Simply model your Azure resources in Bicep and add a connection from your Radius resources. +Radius Applications are able to connect to and leverage every Azure resource with Bicep. Simply model your Azure resources in Bicep and add a connection from your Radius resources. ## Configure an Azure Provider -The Azure provider allows you to deploy and connect to Azure resources from a Radius environment on any of the [supported clusters]({{< ref "/guides/operations/kubernetes/overview#supported-clusters" >}}). To configure an Azure provider, you can follow the documentation [here]({{< ref "/guides/operations/providers/howto-azure-provider" >}}). +The Azure provider allows you to deploy and connect to Azure resources from a Radius Environment on any of the [supported clusters]({{< ref "/guides/operations/kubernetes/overview#supported-clusters" >}}). To configure an Azure provider, you can follow the documentation [here]({{< ref "/guides/operations/providers/howto-azure-provider" >}}). ## Resource library diff --git a/docs/content/guides/author-apps/containers/_index.md b/docs/content/guides/author-apps/containers/_index.md index 8c99dea1f..89add960a 100644 --- a/docs/content/guides/author-apps/containers/_index.md +++ b/docs/content/guides/author-apps/containers/_index.md @@ -2,6 +2,6 @@ type: docs title: "Radius containers" linkTitle: "Containers" -description: "Learn how to model and run container workloads in your Radius application" +description: "Learn how to model and run container workloads in your Radius Application" weight: 200 --- diff --git a/docs/content/guides/author-apps/containers/howto-keyvault-volume/index.md b/docs/content/guides/author-apps/containers/howto-keyvault-volume/index.md index 85dd76afd..bb9808334 100644 --- a/docs/content/guides/author-apps/containers/howto-keyvault-volume/index.md +++ b/docs/content/guides/author-apps/containers/howto-keyvault-volume/index.md @@ -11,7 +11,7 @@ tags: ["Azure","containers"] This how-to guide will provide an overview of how to: -- Setup a Radius environment with an identity provider +- Setup a Radius Environment with an identity provider - Define a connection to an Azure resource with Azure AD role-based access control (RBAC) assignments - Leverage Azure managed identities to connect to an Azure resource - Mount a Key vault as a volume to a container @@ -32,15 +32,15 @@ Begin by running [`rad init --full`]({{< ref rad_init >}}). Make sure to configu rad init --full ``` -## Step 2: Define a Radius environment +## Step 2: Define a Radius Environment -Create a file named `app.bicep` and define a Radius environment with the identity property set: +Create a file named `app.bicep` and define a Radius Environment with the identity property set: {{< rad file="snippets/keyvault-wi.bicep" embed=true marker="//ENVIRONMENT">}} ## Step 3: Define an app, Key Vault, and volume -Add a Radius application, an Azure Key Vault, and a Radius volume which uses the Key Vault to your `app.bicep` file: +Add a Radius Application, an Azure Key Vault, and a Radius volume which uses the Key Vault to your `app.bicep` file: {{< rad file="snippets/keyvault-wi.bicep" embed=true marker="//APP" >}} diff --git a/docs/content/guides/author-apps/containers/howto-volumes/index.md b/docs/content/guides/author-apps/containers/howto-volumes/index.md index 46ff231c8..327145a45 100644 --- a/docs/content/guides/author-apps/containers/howto-volumes/index.md +++ b/docs/content/guides/author-apps/containers/howto-volumes/index.md @@ -16,11 +16,11 @@ This how-to guide will provide an overview of how to: ## Prerequisites - [rad CLI]({{< ref getting-started >}}) -- [Radius environment]({{< ref "/guides/deploy-apps/environments/overview" >}}) +- [Radius Environment]({{< ref "/guides/deploy-apps/environments/overview" >}}) ## Step 1: Define an app and a container -Begin by creating a file named `app.bicep` with a Radius application and [container]({{< ref "guides/author-apps/containers" >}}): +Begin by creating a file named `app.bicep` with a Radius Application and [container]({{< ref "guides/author-apps/containers" >}}): {{< rad file="snippets/1-app.bicep" embed=true >}} diff --git a/docs/content/guides/author-apps/containers/overview/index.md b/docs/content/guides/author-apps/containers/overview/index.md index 50e0cfae9..35665aad8 100644 --- a/docs/content/guides/author-apps/containers/overview/index.md +++ b/docs/content/guides/author-apps/containers/overview/index.md @@ -2,13 +2,13 @@ type: docs title: "Overview: Radius containers" linkTitle: "Overview" -description: "Learn how to model and run container workloads in your Radius application" +description: "Learn how to model and run container workloads in your Radius Application" weight: 100 categories: "Overview" tags: ["containers"] --- -A Radius container enables you to run a container workload as part of your application across different platforms and runtimes. Your container can be a frontend UI, a backend API, a database, or any other container you need to run as part of your app. Plus, with Radius connections, you can easily connect your container to other resources in your application, such as databases, message queues, and more and automatically configure your container with identity, secrets, and other configuration. +A Radius container enables you to run a container workload as part of your application across different platforms and runtimes. Your container can be a frontend UI, a backend API, a database, or any other container you need to run as part of your app. Plus, with Radius Connections, you can easily connect your container to other resources in your application, such as databases, message queues, and more and automatically configure your container with identity, secrets, and other configuration. Container graphic diff --git a/docs/content/guides/author-apps/kubernetes/overview/index.md b/docs/content/guides/author-apps/kubernetes/overview/index.md index 31e43d7ab..5ee31b94f 100644 --- a/docs/content/guides/author-apps/kubernetes/overview/index.md +++ b/docs/content/guides/author-apps/kubernetes/overview/index.md @@ -8,7 +8,7 @@ categories: "Overview" tags: ["Kubernetes"] --- -Radius applications are able to connect to and leverage Kubernetes resources. +Radius Applications are able to connect to and leverage Kubernetes resources. ## Resource library diff --git a/docs/content/guides/author-apps/networking/_index.md b/docs/content/guides/author-apps/networking/_index.md index 8ed58fdf5..f0ed3df8b 100644 --- a/docs/content/guides/author-apps/networking/_index.md +++ b/docs/content/guides/author-apps/networking/_index.md @@ -2,6 +2,6 @@ type: docs title: "Application networking" linkTitle: "Networking" -description: "Learn how to add networking to your Radius application" +description: "Learn how to add networking to your Radius Application" weight: 300 --- diff --git a/docs/content/guides/author-apps/networking/overview/index.md b/docs/content/guides/author-apps/networking/overview/index.md index 4fdda9d7c..acb4395f4 100644 --- a/docs/content/guides/author-apps/networking/overview/index.md +++ b/docs/content/guides/author-apps/networking/overview/index.md @@ -2,7 +2,7 @@ type: docs title: "Overview: Application networking" linkTitle: "Overview" -description: "Learn how to add networking to your Radius application" +description: "Learn how to add networking to your Radius Application" weight: 100 categories: "Overview" --- diff --git a/docs/content/guides/author-apps/portable-resources/overview/index.md b/docs/content/guides/author-apps/portable-resources/overview/index.md index a206743ac..cdae1ac9d 100644 --- a/docs/content/guides/author-apps/portable-resources/overview/index.md +++ b/docs/content/guides/author-apps/portable-resources/overview/index.md @@ -2,7 +2,7 @@ type: docs title: "Overview: Portable Resources" linkTitle: "Overview" -description: "Add portable resources to your Radius application for infrastructure portability" +description: "Add portable resources to your Radius Application for infrastructure portability" weight: 600 categories: "Overview" tags: ["portability"] @@ -10,7 +10,7 @@ tags: ["portability"] ## Overview -Portable resources provide **abstraction** and **portability** to Radius applications. This allows development teams to depend on high level resource types and APIs, and let infra teams swap out the underlying resource and configuration. +Portable resources provide **abstraction** and **portability** to Radius Applications. This allows development teams to depend on high level resource types and APIs, and let infra teams swap out the underlying resource and configuration. Diagram of portable resources connecting to Azure CosmosDB, AWS MongoDB, and a MongoDB Docker container diff --git a/docs/content/guides/author-apps/secrets/_index.md b/docs/content/guides/author-apps/secrets/_index.md index 1c11dc59f..defcb445d 100644 --- a/docs/content/guides/author-apps/secrets/_index.md +++ b/docs/content/guides/author-apps/secrets/_index.md @@ -2,6 +2,6 @@ type: docs title: "Secrets management" linkTitle: "Secrets" -description: "Learn how to create and reference secrets in your Radius application" +description: "Learn how to create and reference secrets in your Radius Application" weight: 500 --- diff --git a/docs/content/guides/author-apps/secrets/overview/index.md b/docs/content/guides/author-apps/secrets/overview/index.md index 512e7f807..745517867 100644 --- a/docs/content/guides/author-apps/secrets/overview/index.md +++ b/docs/content/guides/author-apps/secrets/overview/index.md @@ -2,7 +2,7 @@ type: docs title: "Overview: Secrets management" linkTitle: "Overview" -description: "Learn how to create and reference secrets in your Radius application" +description: "Learn how to create and reference secrets in your Radius Application" weight: 500 categories: "Overview" tags: ["secrets"] @@ -22,7 +22,7 @@ Here is an example for creating a new Secret Store resource and storing a TLS ce ## Reference an existing Secret Store -Here is an example of using a Secret Store to reference secrets stores in an existing secrets management solution that is external to the Radius application stack. Note that only references to Kubernetes Secrets is currently supported, with more to come in the future. +Here is an example of using a Secret Store to reference secrets stores in an existing secrets management solution that is external to the Radius Application stack. Note that only references to Kubernetes Secrets is currently supported, with more to come in the future. {{< rad file="snippets/secretstore.bicep" embed=true marker="//SECRET_STORE_REF" >}} diff --git a/docs/content/guides/author-apps/secrets/overview/snippets/secretstore.bicep b/docs/content/guides/author-apps/secrets/overview/snippets/secretstore.bicep index c618801a4..728b04cf1 100644 --- a/docs/content/guides/author-apps/secrets/overview/snippets/secretstore.bicep +++ b/docs/content/guides/author-apps/secrets/overview/snippets/secretstore.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Injected automatically by the rad CLI.') +@description('The ID of your Radius Environment. Injected automatically by the rad CLI.') param environment string @description('The data for your TLS certificate') diff --git a/docs/content/guides/deploy-apps/_index.md b/docs/content/guides/deploy-apps/_index.md index f94f2a451..644ee0238 100644 --- a/docs/content/guides/deploy-apps/_index.md +++ b/docs/content/guides/deploy-apps/_index.md @@ -2,6 +2,6 @@ type: docs title: "Deploying applications" linkTitle: "Deploying applications" -description: "Learn how to deploy a Radius application to an environment" +description: "Learn how to deploy a Radius Application to an environment" weight: 200 --- \ No newline at end of file diff --git a/docs/content/guides/deploy-apps/environments/howto-environment/index.md b/docs/content/guides/deploy-apps/environments/howto-environment/index.md index 3348f6bb6..3fb961291 100644 --- a/docs/content/guides/deploy-apps/environments/howto-environment/index.md +++ b/docs/content/guides/deploy-apps/environments/howto-environment/index.md @@ -2,15 +2,15 @@ type: docs title: "How-To: Initialize Radius Environments" linkTitle: "Initialize Environments" -description: "Learn how to create Radius environments" +description: "Learn how to create Radius Environments" weight: 200 categories: "How-To" tags: ["environments"] --- -Radius environments are prepared landing zones for applications that contain configuration and Recipes. To learn more visit the [environments overview]({{< ref "/guides/deploy-apps/environments/overview" >}}) page. +Radius Environments are prepared landing zones for applications that contain configuration and Recipes. To learn more visit the [environments overview]({{< ref "/guides/deploy-apps/environments/overview" >}}) page. -Radius environments can be setup with the rad CLI via two paths: interactive or manual. +Radius Environments can be setup with the rad CLI via two paths: interactive or manual. ## Pre-requisites @@ -19,7 +19,7 @@ Radius environments can be setup with the rad CLI via two paths: interactive or ## Create a development environment -1. Initialize a new [Radius environment]({{< ref "/guides/deploy-apps/environments/overview">}}) with [`rad init`]({{< ref rad_init >}}): +1. Initialize a new [Radius Environment]({{< ref "/guides/deploy-apps/environments/overview">}}) with [`rad init`]({{< ref rad_init >}}): ```bash rad init ``` @@ -59,7 +59,7 @@ Radius environments can be setup with the rad CLI via two paths: interactive or ```bash rad env list ``` -3. Use `rad recipe list` to see the list of available recipes: +3. Use `rad recipe list` to see the list of available Recipes: ```bash rad recipe list ``` @@ -68,7 +68,7 @@ Radius environments can be setup with the rad CLI via two paths: interactive or default Applications.Datastores/mongoDatabases bicep radius.azurecr.io/recipes/dev/mongodatabases:latest default Applications.Datastores/redisCaches bicep radius.azurecr.io/recipes/dev/rediscaches:latest ``` - You can follow the [recipes]({{< ref "/guides/recipes/overview" >}}) documentation to learn more about the recipes and how to use them in your application. + You can follow the [Recipes]({{< ref "/guides/recipes/overview" >}}) documentation to learn more about the Recipes and how to use them in your application. ## Create an environment interactively @@ -179,7 +179,7 @@ Radius can also be installed and an environment created with manual rad CLI comm ``` -1. Create your Radius environment: +1. Create your Radius Environment: Run [`rad env create`]({{< ref rad_env_create >}}) to create a new environment in your resource group. Specify the `--namespace` flag to select the Kubernetes namespace to deploy resources into: @@ -187,7 +187,7 @@ Radius can also be installed and an environment created with manual rad CLI comm rad env create myEnvironment --group myGroup --namespace my-namespace ``` - You should see your Radius environment being created and linked to your resource group: + You should see your Radius Environment being created and linked to your resource group: ``` Creating Environment... diff --git a/docs/content/guides/deploy-apps/environments/overview/index.md b/docs/content/guides/deploy-apps/environments/overview/index.md index de1bb45d3..11b4f90ec 100644 --- a/docs/content/guides/deploy-apps/environments/overview/index.md +++ b/docs/content/guides/deploy-apps/environments/overview/index.md @@ -1,14 +1,14 @@ --- type: docs -title: "Overview: Radius environments" +title: "Overview: Radius Environments" linkTitle: "Overview" -description: "Learn about Radius environments and how to interact with them" +description: "Learn about Radius Environments and how to interact with them" weight: 100 categories: "Overview" tags: ["environments"] --- -Radius environments are prepared "landing zones" for Radius applications. Applications deployed to an environment will inherit the container runtime, configuration, and other settings from the environment. Stay tuned for additional environment capabilities coming soon. +Radius Environments are prepared "landing zones" for Radius Applications. Applications deployed to an environment will inherit the container runtime, configuration, and other settings from the environment. Stay tuned for additional environment capabilities coming soon. ## Configuration @@ -16,11 +16,11 @@ The following configuration options are available for environments: ### Container runtime -Radius environments can be configured with a container runtime, where Radius [containers]({{< ref "guides/author-apps/containers" >}}) will be run, along with [gateways and routes]({{< ref networking >}}). +Radius Environments can be configured with a container runtime, where Radius [containers]({{< ref "guides/author-apps/containers" >}}) will be run, along with [gateways and routes]({{< ref networking >}}). A Kubernetes namespace is specified on the environment to tell Radius where to render application resources at deploy time. -Diagram showing a Radius environment mapping to a Kubernetes cluster and namespace +Diagram showing a Radius Environment mapping to a Kubernetes cluster and namespace ### Cloud Provider @@ -43,7 +43,7 @@ Supported identity providers: ## CLI commands -The following commands let you interact with Radius environments: +The following commands let you interact with Radius Environments: {{< tabs init list show delete switch >}} diff --git a/docs/content/guides/deploy-apps/howto-delete/index.md b/docs/content/guides/deploy-apps/howto-delete/index.md index cc656edf8..ff1275a3b 100644 --- a/docs/content/guides/deploy-apps/howto-delete/index.md +++ b/docs/content/guides/deploy-apps/howto-delete/index.md @@ -1,8 +1,8 @@ --- type: docs -title: "How-To: Delete an application from a Radius environment" +title: "How-To: Delete an application from a Radius Environment" linkTitle: "Delete apps" -description: "Learn how to delete a Radius application" +description: "Learn how to delete a Radius Application" weight: 400 categories: "How-To" tags: ["delete"] @@ -10,24 +10,24 @@ tags: ["delete"] ## Pre-requisites -- A [deployed application]({{< ref deploy-apps >}}) in a Radius environment. +- A [deployed application]({{< ref deploy-apps >}}) in a Radius Environment. -## Step 1: Delete the Radius application from the environment +## Step 1: Delete the Radius Application from the environment -You can delete the Radius application using the [`rad app delete`]({{< ref rad_application_delete >}}) command: +You can delete the Radius Application using the [`rad app delete`]({{< ref rad_application_delete >}}) command: ```bash rad app delete ``` -This will delete the following resources from the Radius environment +This will delete the following resources from the Radius Environment 1. All the resources created by Radius on the Kubernetes cluster under the `-` namespace 2. All the resources provisioned by Recipes ## Step 2: Delete any cloud/platform resources -AWS, Azure, Kubernetes, and any other cloud/platform resources that were deployed alongside your Radius application and not as part of a Recipe need to be deleted as a separate step. +AWS, Azure, Kubernetes, and any other cloud/platform resources that were deployed alongside your Radius Application and not as part of a Recipe need to be deleted as a separate step. {{< tabs Azure AWS Kubernetes >}} diff --git a/docs/content/guides/deploy-apps/howto-deploy/_index.md b/docs/content/guides/deploy-apps/howto-deploy/_index.md index 388ee9f54..91afa66c7 100644 --- a/docs/content/guides/deploy-apps/howto-deploy/_index.md +++ b/docs/content/guides/deploy-apps/howto-deploy/_index.md @@ -2,6 +2,6 @@ type: docs title: "Deploying applications" linkTitle: "Deploy apps" -description: "Learn how to deploy a Radius application to an environment" +description: "Learn how to deploy a Radius Application to an environment" weight: 300 --- \ No newline at end of file diff --git a/docs/content/guides/deploy-apps/howto-deploy/howto-deploy-cicd/index.md b/docs/content/guides/deploy-apps/howto-deploy/howto-deploy-cicd/index.md index d34332308..556e2ebf9 100644 --- a/docs/content/guides/deploy-apps/howto-deploy/howto-deploy-cicd/index.md +++ b/docs/content/guides/deploy-apps/howto-deploy/howto-deploy-cicd/index.md @@ -100,7 +100,7 @@ Next, download the latest `rad` CLI release and setup your workspace: wget -q "https://get.radapp.dev/tools/rad/install.sh" -O - | /bin/bash ./rad bicep download ./rad --version - - name: Initialize Radius environment + - name: Initialize Radius Environment run: | ./rad group create default ./rad workspace create kubernetes default --group default diff --git a/docs/content/guides/deploy-apps/howto-deploy/howto-deploy-rad-cli/index.md b/docs/content/guides/deploy-apps/howto-deploy/howto-deploy-rad-cli/index.md index 330bdd74a..407f39bf4 100644 --- a/docs/content/guides/deploy-apps/howto-deploy/howto-deploy-rad-cli/index.md +++ b/docs/content/guides/deploy-apps/howto-deploy/howto-deploy-rad-cli/index.md @@ -1,17 +1,17 @@ --- type: docs -title: "How-To: Deploying applications into a Radius environment" +title: "How-To: Deploying applications into a Radius Environment" linkTitle: "Deploy via CLI" -description: "Learn how to deploy a Radius application" +description: "Learn how to deploy a Radius Application" weight: 200 categories: "How-To" tags: ["deployments"] --- ## Pre-requisites -- [An authored Radius application]({{< ref author-apps >}}) +- [An authored Radius Application]({{< ref author-apps >}}) -## Step 1 : Deploy an application into a Radius environment +## Step 1 : Deploy an application into a Radius Environment {{< tabs Deploy-app Deploy-app-with-parameters >}} @@ -21,7 +21,7 @@ An application can be deployed to an environment with [`rad deploy`]({{< ref rad ```bash rad deploy app.bicep ``` - This will deploy the application to the created Radius environment. + This will deploy the application to the created Radius Environment. {{% /codetab %}} {{% codetab %}} @@ -31,12 +31,12 @@ Parameters can be included as part of `rad deploy` via the `-p/--parameters` fla rad deploy app.bicep -p param1=value1 -p param2=value2 ``` - This will deploy the application to the created Radius environment injecting the parameters into the application. + This will deploy the application to the created Radius Environment injecting the parameters into the application. You can find more examples of deploying applications with parameters [here]({{< ref "rad_deploy#examples" >}}). {{% /codetab %}} {{< /tabs >}} - > Follow the [how-to guide]({{< ref howto-troubleshootapps >}}) for guidance on troubleshooting your Radius application + > Follow the [how-to guide]({{< ref howto-troubleshootapps >}}) for guidance on troubleshooting your Radius Application diff --git a/docs/content/guides/deploy-apps/howto-deploy/howto-run-app/index.md b/docs/content/guides/deploy-apps/howto-deploy/howto-run-app/index.md index 3fb95d385..baf03af94 100644 --- a/docs/content/guides/deploy-apps/howto-deploy/howto-run-app/index.md +++ b/docs/content/guides/deploy-apps/howto-deploy/howto-run-app/index.md @@ -9,7 +9,7 @@ tags: ["deployments"] --- ## Pre-requisites -- [An authored Radius application]({{< ref author-apps >}}) +- [An authored Radius Application]({{< ref author-apps >}}) ## Step 1: Run an application @@ -32,7 +32,7 @@ Parameters can be included as part of `rad run` via the `-p/--parameters` flag: rad run app.bicep -p param1=value1 -p param2=value2 ``` -This will deploy the application to the created Radius environment injecting the parameters into the application. +This will deploy the application to the created Radius Environment injecting the parameters into the application. You can find more examples of deploying applications with parameters [here]({{< ref "rad_run#examples" >}}). {{% /codetab %}} diff --git a/docs/content/guides/deploy-apps/howto-troubleshootapps/index.md b/docs/content/guides/deploy-apps/howto-troubleshootapps/index.md index 73a7737a0..a950b76ed 100644 --- a/docs/content/guides/deploy-apps/howto-troubleshootapps/index.md +++ b/docs/content/guides/deploy-apps/howto-troubleshootapps/index.md @@ -2,7 +2,7 @@ type: docs title: "How-To: Troubleshoot applications" linkTitle: "Troubleshoot apps" -description: "Learn how to troubleshoot issues with the Radius application" +description: "Learn how to troubleshoot issues with the Radius Application" weight: 900 categories: "How-To" tags: ["troubleshooting"] @@ -10,7 +10,7 @@ tags: ["troubleshooting"] ## Pre-requisites -- A [deployed application]({{< ref deploy-apps >}}) in a Radius environment. +- A [deployed application]({{< ref deploy-apps >}}) in a Radius Environment. ## Step 1: Port-forward container to your local machine @@ -23,7 +23,7 @@ Refer to [`rad resource expose`]({{< ref rad_resource_expose >}}) for more detai ## Step 2: Inspect container logs -If your Radius application is unresponsive or does not connect to its dependencies, Use the below command to inspect logs from container: +If your Radius Application is unresponsive or does not connect to its dependencies, Use the below command to inspect logs from container: ```bash rad resource logs containers frontend -a diff --git a/docs/content/guides/operations/_index.md b/docs/content/guides/operations/_index.md index d0eb2d045..8356acae6 100644 --- a/docs/content/guides/operations/_index.md +++ b/docs/content/guides/operations/_index.md @@ -2,6 +2,6 @@ type: docs title: "Environment operations guides" linkTitle: "Operations" -description: "Learn how to deploy and operate Radius environments" +description: "Learn how to deploy and operate Radius Environments" weight: 400 --- diff --git a/docs/content/guides/operations/control-plane/howto-postman/index.md b/docs/content/guides/operations/control-plane/howto-postman/index.md index 76563a31e..065fb3232 100644 --- a/docs/content/guides/operations/control-plane/howto-postman/index.md +++ b/docs/content/guides/operations/control-plane/howto-postman/index.md @@ -124,13 +124,13 @@ Next, you'll need to get the control plane API endpoint and use Postman to inter ] } ``` -1. Update your request URL to [list all the Radius environments]({{< ref api-environments >}}) in your resource group (_make sure to update the name of your resource group in the URL. In this example the resource group name is default_): +1. Update your request URL to [list all the Radius Environments]({{< ref api-environments >}}) in your resource group (_make sure to update the name of your resource group in the URL. In this example the resource group name is default_): ``` /apis/api.ucp.dev/v1alpha3/planes/radius/local/resourcegroups/default/providers/Applications.Core/environments?api-version=2023-10-01-preview ``` - You should now see your Radius environment(s): + You should now see your Radius Environment(s): ``` { diff --git a/docs/content/guides/operations/groups/howto-resourcegroups/index.md b/docs/content/guides/operations/groups/howto-resourcegroups/index.md index 5ab4a4681..9ebac615b 100644 --- a/docs/content/guides/operations/groups/howto-resourcegroups/index.md +++ b/docs/content/guides/operations/groups/howto-resourcegroups/index.md @@ -4,6 +4,7 @@ title: "How-To: Manage resource groups" linkTitle: "Manage groups" description: "Learn how to manage resource groups in Radius" weight: 200 +categories: "How-To" --- This guide will walk you through the process of managing resource groups in Radius. For more information on resource groups, see [Resource groups]({{< ref groups >}}). diff --git a/docs/content/guides/operations/groups/overview/index.md b/docs/content/guides/operations/groups/overview/index.md index 675f90e3a..b7d182fee 100644 --- a/docs/content/guides/operations/groups/overview/index.md +++ b/docs/content/guides/operations/groups/overview/index.md @@ -6,7 +6,7 @@ description: "Learn how to manage collections of resources with resource groups" weight: 100 --- -Resource groups are collections of resources that you can manage as a single unit. You can use resource groups to organize your resources when deploying Radius applications. +Resource groups are collections of resources that you can manage as a single unit. You can use resource groups to organize your resources when deploying Radius Applications. Diagram showing Radius resources inside of a Radius resource group diff --git a/docs/content/guides/operations/kubernetes/kubernetes-upgrade/index.md b/docs/content/guides/operations/kubernetes/kubernetes-upgrade/index.md index 463ef49a5..600eb76d6 100644 --- a/docs/content/guides/operations/kubernetes/kubernetes-upgrade/index.md +++ b/docs/content/guides/operations/kubernetes/kubernetes-upgrade/index.md @@ -9,9 +9,9 @@ categories: "How-To" Radius does not offer backward compatibility with previous releases. Breaking changes may happen between releases and we recommend doing a fresh installation of the latest version of Radius after every release. -## Step 1 : Delete any existing Radius environments +## Step 1 : Delete any existing Radius Environments -To delete any existing Radius environments, run the following command: +To delete any existing Radius Environments, run the following command: ```bash rad env delete @@ -33,6 +33,6 @@ rad uninstall kubernetes {{< read file= "/shared-content/installation/vscode-bicep/install-vscode-bicep.md" >}} -## Step 5: Initialize the Radius control-plane and the Radius environment +## Step 5: Initialize the Radius control-plane and the Radius Environment {{< read file= "/shared-content/installation/install-radius/initialize-radius.md" >}} diff --git a/docs/content/guides/operations/kubernetes/overview/index.md b/docs/content/guides/operations/kubernetes/overview/index.md index 82f526f8c..9174dcd95 100644 --- a/docs/content/guides/operations/kubernetes/overview/index.md +++ b/docs/content/guides/operations/kubernetes/overview/index.md @@ -8,7 +8,7 @@ categories: ["Overview"] tags: ["Kubernetes"] --- -Radius offers a Kubernetes-based platform for hosting the [Radius control plane]({{< ref "/guides/operations/control-plane" >}}) and [Radius environments]({{< ref "/guides/deploy-apps/environments/overview" >}}). +Radius offers a Kubernetes-based platform for hosting the [Radius control plane]({{< ref "/guides/operations/control-plane" >}}) and [Radius Environments]({{< ref "/guides/deploy-apps/environments/overview" >}}). Diagram showing Radius resources being mapped to Kubernetes objects @@ -44,7 +44,7 @@ For multiple Radius resources that map to a single Kubernetes resource (_e.g. da ## Kubernetes metadata -Radius environments, applications, and resources can be annotated/labeled with Kubernetes metadata. Refer to the Kubernetes metadata page for more information: +Radius Environments, applications, and resources can be annotated/labeled with Kubernetes metadata. Refer to the Kubernetes metadata page for more information: {{< button text="Kubernetes metadata" page="kubernetes-metadata" >}} @@ -55,7 +55,7 @@ The following clusters have been tested and validated to ensure they support all {{< tabs AKS k3d kind EKS >}} {{% codetab %}} -Azure Kubernetes Service (AKS) clusters are the easiest way to get up and running quickly with a Radius environment. To learn how to setup a cluster visit the [Azure docs](https://docs.microsoft.com/azure/aks/learn/quick-kubernetes-deploy-portal?tabs=azure-cli). +Azure Kubernetes Service (AKS) clusters are the easiest way to get up and running quickly with a Radius Environment. To learn how to setup a cluster visit the [Azure docs](https://docs.microsoft.com/azure/aks/learn/quick-kubernetes-deploy-portal?tabs=azure-cli). Note that [AKS-managed AAD](https://docs.microsoft.com/en-us/azure/aks/managed-aad) is not supported currently. @@ -66,7 +66,7 @@ az aks create --subscription mySubscription --resource-group myResourceGroup --n az aks get-credentials --subscription mySubscription --resource-group myResourceGroup --name myAKSCluster ``` -Once deployed and your kubectl context has been set as your default, you can run the following to create a Radius environment and install the control plane: +Once deployed and your kubectl context has been set as your default, you can run the following to create a Radius Environment and install the control plane: ```bash rad init @@ -117,7 +117,7 @@ nodes: listenAddress: "0.0.0.0" ``` -Then, create a kind cluster with this config and initialize your Radius environment: +Then, create a kind cluster with this config and initialize your Radius Environment: ```bash # Create the kind cluster kind create cluster --config kind-config.yaml @@ -139,7 +139,7 @@ Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that you can eksctl create cluster --name my-cluster --region region-code ``` -Once deployed and your kubectl context has been set as your default, you can run the following to create a Radius environment and install the control plane: +Once deployed and your kubectl context has been set as your default, you can run the following to create a Radius Environment and install the control plane: ```bash rad init diff --git a/docs/content/guides/operations/providers/howto-aws-provider/index.md b/docs/content/guides/operations/providers/howto-aws-provider/index.md index f273d3bf3..e96a1e89d 100644 --- a/docs/content/guides/operations/providers/howto-aws-provider/index.md +++ b/docs/content/guides/operations/providers/howto-aws-provider/index.md @@ -2,13 +2,13 @@ type: docs title: "How-To: Configure the AWS cloud provider" linkTitle: "Configure AWS provider" -description: "Learn how to configure the AWS provider for your Radius environment" +description: "Learn how to configure the AWS provider for your Radius Environment" weight: 300 categories: "How-To" tags: ["AWS"] --- -The AWS provider allows you to deploy and connect to AWS resources from a Radius environment on an EKS cluster. It can be configured: +The AWS provider allows you to deploy and connect to AWS resources from a Radius Environment on an EKS cluster. It can be configured: - [Interactively via `rad init`](#interactive-configuration) - [Manually via `rad env update` and `rad credential register`](#manual-configuration) diff --git a/docs/content/guides/operations/providers/howto-azure-provider/index.md b/docs/content/guides/operations/providers/howto-azure-provider/index.md index 22e1335d3..6bdf31073 100644 --- a/docs/content/guides/operations/providers/howto-azure-provider/index.md +++ b/docs/content/guides/operations/providers/howto-azure-provider/index.md @@ -2,13 +2,13 @@ type: docs title: "How-To: Configure the Azure cloud provider" linkTitle: "Configure Azure provider" -description: "Learn how to configure the Azure provider for your Radius environment" +description: "Learn how to configure the Azure provider for your Radius Environment" weight: 200 categories: "How-To" tags: ["Azure"] --- -The Azure provider allows you to deploy and connect to Azure resources from a self-hosted Radius environment. It can be configured: +The Azure provider allows you to deploy and connect to Azure resources from a self-hosted Radius Environment. It can be configured: - [Interactively via `rad init`](#interactive-configuration) - [Manually via `rad env update` and `rad credential register`](#manual-configuration) diff --git a/docs/content/guides/operations/workspaces/overview/index.md b/docs/content/guides/operations/workspaces/overview/index.md index e6ff96d64..83e1cc75f 100644 --- a/docs/content/guides/operations/workspaces/overview/index.md +++ b/docs/content/guides/operations/workspaces/overview/index.md @@ -13,7 +13,7 @@ Workspaces allow you to manage multiple Radius platforms and environments using ## CLI commands -The following commands let you interact with Radius environments: +The following commands let you interact with Radius Environments: {{< tabs create list show delete switch >}} diff --git a/docs/content/guides/recipes/_index.md b/docs/content/guides/recipes/_index.md index 4af065e94..cf593bf01 100644 --- a/docs/content/guides/recipes/_index.md +++ b/docs/content/guides/recipes/_index.md @@ -2,6 +2,6 @@ type: docs title: "Radius Recipes" linkTitle: "Recipes" -description: "Learn how to automate infrastructure deployment for your resources with Radius recipes" +description: "Learn how to automate infrastructure deployment for your resources with Radius Recipes" weight: 300 --- diff --git a/docs/content/guides/recipes/howto-author-recipes/index.md b/docs/content/guides/recipes/howto-author-recipes/index.md index 5599d81a6..12ccea392 100644 --- a/docs/content/guides/recipes/howto-author-recipes/index.md +++ b/docs/content/guides/recipes/howto-author-recipes/index.md @@ -120,7 +120,7 @@ Follow the [Terraform module publishing docs](https://developer.hashicorp.com/te ### Step 5: Register your Recipe with your environment -Now that your Recipe template has been stored, you can add it your Radius environment to be used by developers. This allows you to mix-and-match templates for each of your environments such as dev, canary, and prod. +Now that your Recipe template has been stored, you can add it your Radius Environment to be used by developers. This allows you to mix-and-match templates for each of your environments such as dev, canary, and prod. {{< tabs "rad CLI - Bicep" "rad CLI - Terraform" "Bicep environment" >}} diff --git a/docs/content/guides/recipes/overview/index.md b/docs/content/guides/recipes/overview/index.md index dddcd64ca..9b9d3837e 100644 --- a/docs/content/guides/recipes/overview/index.md +++ b/docs/content/guides/recipes/overview/index.md @@ -2,7 +2,7 @@ type: docs title: "Overview: Radius Recipes" linkTitle: "Overview" -description: "Learn how to automate infrastructure deployment for your resources with Radius recipes" +description: "Learn how to automate infrastructure deployment for your resources with Radius Recipes" weight: 100 categories: "Overview" tags: ["recipes"] @@ -35,7 +35,7 @@ Use [**rad recipe list**]({{< ref rad_recipe_list >}}) to view the Recipes avail ### Use lightweight "local-dev" Recipes -Radius environments make it easy to get up and running with Recipes instantly. When you run [`rad init`]({{< ref rad_init >}}) you get a set of containerized local-dev Recipes pre-registered in your environment. These Recipes are designed to help you get started quickly with Recipes using lightweight containers. You can use these Recipes to test your app locally, or deploy them to a dev environment. +Radius Environments make it easy to get up and running with Recipes instantly. When you run [`rad init`]({{< ref rad_init >}}) you get a set of containerized local-dev Recipes pre-registered in your environment. These Recipes are designed to help you get started quickly with Recipes using lightweight containers. You can use these Recipes to test your app locally, or deploy them to a dev environment. ### Customize with parameters diff --git a/docs/content/guides/tooling/rad-cli/overview/index.md b/docs/content/guides/tooling/rad-cli/overview/index.md index d47de94f3..6cfd8f96d 100644 --- a/docs/content/guides/tooling/rad-cli/overview/index.md +++ b/docs/content/guides/tooling/rad-cli/overview/index.md @@ -18,13 +18,13 @@ Usage: rad [command] Available Commands: - application Manage Radius applications + application Manage Radius Applications bicep Manage bicep compiler completion Generates shell completion scripts credential Manage cloud provider credential for a Radius installation. debug-logs Capture logs from Radius control plane for debugging and diagnostics. deploy Deploy a template - env Manage Radius environments + env Manage Radius Environments group Manage resource groups help Help about any command init Initialize Radius diff --git a/docs/content/guides/tooling/vscode/overview/index.md b/docs/content/guides/tooling/vscode/overview/index.md index 3eea5d1b1..503601b29 100644 --- a/docs/content/guides/tooling/vscode/overview/index.md +++ b/docs/content/guides/tooling/vscode/overview/index.md @@ -8,7 +8,7 @@ categories: "Overview" tags: ["VSCode"] --- -When using Visual Studio Code with Radius there are a set of extensions you can install to help author, validate, and manage your Radius applications and environments. +When using Visual Studio Code with Radius there are a set of extensions you can install to help author, validate, and manage your Radius Applications and environments. ## Radius Bicep extension diff --git a/docs/content/installation/index.md b/docs/content/installation/index.md index ed79a0d7a..d73dc5cee 100644 --- a/docs/content/installation/index.md +++ b/docs/content/installation/index.md @@ -18,7 +18,7 @@ Radius consists of a set of tools and services that together form the Radius pla {{< read file= "/shared-content/installation/vscode-bicep/install-vscode-bicep.md" >}} -## Step 3: Initialize the Radius control-plane and the Radius environment +## Step 3: Initialize the Radius control-plane and the Radius Environment {{< read file= "/shared-content/installation/install-radius/initialize-radius.md" >}} diff --git a/docs/content/reference/config.md b/docs/content/reference/config.md index d14735201..fd8faea45 100644 --- a/docs/content/reference/config.md +++ b/docs/content/reference/config.md @@ -63,7 +63,7 @@ workspaces: | Key | Description | Example | |-----|-------------|---------| | **context** | The name of the Kubernetes context to use | `DevCluster` | -| **namespace** | The name of the Kubernetes namespace to use when deploying Radius applications | `default` | +| **namespace** | The name of the Kubernetes namespace to use when deploying Radius Applications | `default` | #### providerConfig diff --git a/docs/content/reference/faq.md b/docs/content/reference/faq.md index a67d30320..e24d471d6 100644 --- a/docs/content/reference/faq.md +++ b/docs/content/reference/faq.md @@ -14,7 +14,7 @@ Currently yes. Today Kubernetes is the only hosting platform for Radius. We are ### Can I incrementally adopt, or "try out" Radius? -Yes. Teams can incrementally adopt the Radius platform as they write new applications or add existing applications. Direct connections allow apps with existing platform dependencies (such as Azure and AWS) move to Radius without any code rewrites. Dapr support allows existing Dapr apps to be brought to Radius without any code rewrites as well. Portability and automation can be layered on with Radius portable resources and Recipes. In the future we will add Kubernetes YAML support which enables developers to wrap their existing Kubernetes YAML objects in a Radius container so that they may bring their existing deployments and pods as-is into a Radius application. +Yes. Teams can incrementally adopt the Radius platform as they write new applications or add existing applications. Direct connections allow apps with existing platform dependencies (such as Azure and AWS) move to Radius without any code rewrites. Dapr support allows existing Dapr apps to be brought to Radius without any code rewrites as well. Portability and automation can be layered on with Radius portable resources and Recipes. In the future we will add Kubernetes YAML support which enables developers to wrap their existing Kubernetes YAML objects in a Radius container so that they may bring their existing deployments and pods as-is into a Radius Application. ### Do I have to self-host Radius? Is there a managed service for Radius? @@ -53,7 +53,7 @@ Recipes currently support the set of Radius portable resources: Redis, Mongo, Ra ### Do developers need contributor or owner access to a cloud provider (Azure subscription, AWS account, etc.) to leverage Radius Recipes? -No. Recipes are deployed on-behalf-of the Radius environment so developers do not need any write access to an Azure subscription, resource group, or AWS account. This allows a least-privilege access model to cloud resources and for IT operators to only allow approved IaC templates to be deployed to their cloud environments. +No. Recipes are deployed on-behalf-of the Radius Environment so developers do not need any write access to an Azure subscription, resource group, or AWS account. This allows a least-privilege access model to cloud resources and for IT operators to only allow approved IaC templates to be deployed to their cloud environments. ### Why do I need to manually output a Kubernetes UCP ID as part of my Bicep Recipe? @@ -98,11 +98,11 @@ Yes. You will need to modify the resource definition in your .bicep file's appli ### What AWS services does Radius support -Radius applications can include AWS services that are also supported by the AWS cloud control API. See the [AWS resource library]({{< ref "/guides/author-apps/aws/overview#resource-library" >}}) for the complete list of supported AWS resources. Radius does not currently support direct connections to AWS resources, but it is on the backlog. Stay tuned for updates. +Radius Applications can include AWS services that are also supported by the AWS cloud control API. See the [AWS resource library]({{< ref "/guides/author-apps/aws/overview#resource-library" >}}) for the complete list of supported AWS resources. Radius does not currently support direct connections to AWS resources, but it is on the backlog. Stay tuned for updates. ### What Azure services does Radius support? -Radius applications can include any non-compute Azure service, with support for direct connections and managed identities. Compute services (Web Apps, Container Apps, App Service, Functions, Logic Apps, and others) will be added in a future release. +Radius Applications can include any non-compute Azure service, with support for direct connections and managed identities. Compute services (Web Apps, Container Apps, App Service, Functions, Logic Apps, and others) will be added in a future release. ### Does Radius support Google Cloud Platform (GCP)? diff --git a/docs/content/reference/limitations.md b/docs/content/reference/limitations.md index 8bde0ee26..0e6cd31d2 100644 --- a/docs/content/reference/limitations.md +++ b/docs/content/reference/limitations.md @@ -24,7 +24,7 @@ This will be addressed further in a future release. ### Changing the Kubernetes namespace of an environment or application requires the app to be deleted and redeployed -A Radius environment allows you to specify Kubernetes as your compute platform, as well as specify the Kubernetes namespace in which Kubernetes objects are deployed. Additionally, you can override the namespace for a specific application using the [kubernetesNamespace extension.]({{< ref "application-schema#kubernetesNamespace" >}}). Currently, changing the namespace of an environment or application requires the application to be deleted and redeployed. If you need to change the namespace of an application, you can do so by deleting the application and/or environment and redeploying it with the new namespace. +A Radius Environment allows you to specify Kubernetes as your compute platform, as well as specify the Kubernetes namespace in which Kubernetes objects are deployed. Additionally, you can override the namespace for a specific application using the [kubernetesNamespace extension.]({{< ref "application-schema#kubernetesNamespace" >}}). Currently, changing the namespace of an environment or application requires the application to be deleted and redeployed. If you need to change the namespace of an application, you can do so by deleting the application and/or environment and redeploying it with the new namespace. ### Resource names cannot contain underscores (_) @@ -90,6 +90,6 @@ Some of the [AWS resource types](/resource-schema/aws) are 'non-idempotent', thi We are currently building support for non-idempotent resources in Radius. Please like and comment on this [this issue](https://github.com/radius-project/radius/issues/6227) if you are interested in the same. -As a workaround, you can try using [terraform recipes](https://docs.radapp.dev/guides/recipes/overview/) to deploy and manage those non-idempotent resource types. +As a workaround, you can try using [Terraform Recipes](https://docs.radapp.dev/guides/recipes/overview/) to deploy and manage those non-idempotent resource types. diff --git a/docs/content/reference/resource-schema/_index.md b/docs/content/reference/resource-schema/_index.md index 5aa2d9ed9..c4c19f48e 100644 --- a/docs/content/reference/resource-schema/_index.md +++ b/docs/content/reference/resource-schema/_index.md @@ -2,7 +2,7 @@ type: docs title: "Resource schemas" linkTitle: "Resource schemas" -description: "Schema docs for the resources that can comprise a Radius application" +description: "Schema docs for the resources that can comprise a Radius Application" weight: 300 --- diff --git a/docs/content/reference/resource-schema/cache/redis/snippets/redis-manual.bicep b/docs/content/reference/resource-schema/cache/redis/snippets/redis-manual.bicep index f7407d3b6..ace56121b 100644 --- a/docs/content/reference/resource-schema/cache/redis/snippets/redis-manual.bicep +++ b/docs/content/reference/resource-schema/cache/redis/snippets/redis-manual.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/reference/resource-schema/cache/redis/snippets/redis-recipe.bicep b/docs/content/reference/resource-schema/cache/redis/snippets/redis-recipe.bicep index 4a2138d5d..c41b30c84 100644 --- a/docs/content/reference/resource-schema/cache/redis/snippets/redis-recipe.bicep +++ b/docs/content/reference/resource-schema/cache/redis/snippets/redis-recipe.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/reference/resource-schema/core-schema/application-schema/_index.md b/docs/content/reference/resource-schema/core-schema/application-schema/_index.md index d6855ed02..f6ab3ad1d 100644 --- a/docs/content/reference/resource-schema/core-schema/application-schema/_index.md +++ b/docs/content/reference/resource-schema/core-schema/application-schema/_index.md @@ -40,7 +40,7 @@ The Kubernetes namespace extension allows you to customize how all of the resour ##### kubernetesMetadata -The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubernetes-metadata">}}) enables you set and cascade Kubernetes metadata such as labels and Annotations on all the Kubernetes resources defined with in your Radius application. For examples, please refer to the extension overview page. +The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubernetes-metadata">}}) enables you set and cascade Kubernetes metadata such as labels and Annotations on all the Kubernetes resources defined with in your Radius Application. For examples, please refer to the extension overview page. ###### Properties diff --git a/docs/content/reference/resource-schema/core-schema/container-schema/_index.md b/docs/content/reference/resource-schema/core-schema/container-schema/_index.md index ee8e6db1f..01cb936d7 100644 --- a/docs/content/reference/resource-schema/core-schema/container-schema/_index.md +++ b/docs/content/reference/resource-schema/core-schema/container-schema/_index.md @@ -2,7 +2,7 @@ type: docs title: "Container service" linkTitle: "Container" -description: "Learn how to add a container to your Radius application" +description: "Learn how to add a container to your Radius Application" weight: 300 --- @@ -119,7 +119,7 @@ Additional properties are available and required depending on the 'kind' of the #### kubernetesMetadata -The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubernetes-metadata">}}) enables you set and cascade Kubernetes metadata such as labels and Annotations on all the Kubernetes resources defined with in your Radius application. For examples refer to the extension overview page. +The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubernetes-metadata">}}) enables you set and cascade Kubernetes metadata such as labels and Annotations on all the Kubernetes resources defined with in your Radius Application. For examples refer to the extension overview page. ##### Properties diff --git a/docs/content/reference/resource-schema/core-schema/environment-schema/index.md b/docs/content/reference/resource-schema/core-schema/environment-schema/index.md index 924ef1333..9e7fe5932 100644 --- a/docs/content/reference/resource-schema/core-schema/environment-schema/index.md +++ b/docs/content/reference/resource-schema/core-schema/environment-schema/index.md @@ -65,7 +65,7 @@ Extensions allow you to customize how resources are generated or customized as p #### kubernetesMetadata -The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubernetes-metadata">}}) enables you set and cascade Kubernetes metadata such as labels and Annotations on all the Kubernetes resources defined with in your Radius application. For examples, please refer to the extension overview page. +The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubernetes-metadata">}}) enables you set and cascade Kubernetes metadata such as labels and Annotations on all the Kubernetes resources defined with in your Radius Application. For examples, please refer to the extension overview page. ##### Properties @@ -89,4 +89,4 @@ The [Kubernetes Metadata extension]({{< ref "guides/operations/kubernetes/kubern ## Further reading -- [Radius environments]({{< ref "/guides/deploy-apps/environments/overview" >}}) +- [Radius Environments]({{< ref "/guides/deploy-apps/environments/overview" >}}) diff --git a/docs/content/reference/resource-schema/dapr-schema/dapr-extension/snippets/dapr.bicep b/docs/content/reference/resource-schema/dapr-schema/dapr-extension/snippets/dapr.bicep index 7f9f4ee36..ee9035afa 100644 --- a/docs/content/reference/resource-schema/dapr-schema/dapr-extension/snippets/dapr.bicep +++ b/docs/content/reference/resource-schema/dapr-schema/dapr-extension/snippets/dapr.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/reference/resource-schema/dapr-schema/dapr-pubsub/snippets/dapr-pubsub-manual.bicep b/docs/content/reference/resource-schema/dapr-schema/dapr-pubsub/snippets/dapr-pubsub-manual.bicep index 071deb02b..f37ccd3dd 100644 --- a/docs/content/reference/resource-schema/dapr-schema/dapr-pubsub/snippets/dapr-pubsub-manual.bicep +++ b/docs/content/reference/resource-schema/dapr-schema/dapr-pubsub/snippets/dapr-pubsub-manual.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/reference/resource-schema/dapr-schema/dapr-pubsub/snippets/dapr-pubsub-recipe.bicep b/docs/content/reference/resource-schema/dapr-schema/dapr-pubsub/snippets/dapr-pubsub-recipe.bicep index fd76666f9..0b7131a55 100644 --- a/docs/content/reference/resource-schema/dapr-schema/dapr-pubsub/snippets/dapr-pubsub-recipe.bicep +++ b/docs/content/reference/resource-schema/dapr-schema/dapr-pubsub/snippets/dapr-pubsub-recipe.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/reference/resource-schema/dapr-schema/dapr-secretstore/snippets/dapr-secretstore-manual.bicep b/docs/content/reference/resource-schema/dapr-schema/dapr-secretstore/snippets/dapr-secretstore-manual.bicep index 9623150f0..9aeefc246 100644 --- a/docs/content/reference/resource-schema/dapr-schema/dapr-secretstore/snippets/dapr-secretstore-manual.bicep +++ b/docs/content/reference/resource-schema/dapr-schema/dapr-secretstore/snippets/dapr-secretstore-manual.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/reference/resource-schema/dapr-schema/dapr-secretstore/snippets/dapr-secretstore-recipe.bicep b/docs/content/reference/resource-schema/dapr-schema/dapr-secretstore/snippets/dapr-secretstore-recipe.bicep index 9b2a15ae6..73168cca9 100644 --- a/docs/content/reference/resource-schema/dapr-schema/dapr-secretstore/snippets/dapr-secretstore-recipe.bicep +++ b/docs/content/reference/resource-schema/dapr-schema/dapr-secretstore/snippets/dapr-secretstore-recipe.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/reference/resource-schema/dapr-schema/dapr-statestore/snippets/dapr-statestore-manual.bicep b/docs/content/reference/resource-schema/dapr-schema/dapr-statestore/snippets/dapr-statestore-manual.bicep index 1009cf597..eab0d2522 100644 --- a/docs/content/reference/resource-schema/dapr-schema/dapr-statestore/snippets/dapr-statestore-manual.bicep +++ b/docs/content/reference/resource-schema/dapr-schema/dapr-statestore/snippets/dapr-statestore-manual.bicep @@ -1,9 +1,9 @@ import radius as radius -@description('The app ID of your Radius application. Set automatically by the rad CLI.') +@description('The app ID of your Radius Application. Set automatically by the rad CLI.') param application string -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string //SAMPLE diff --git a/docs/content/reference/resource-schema/dapr-schema/dapr-statestore/snippets/dapr-statestore-recipe.bicep b/docs/content/reference/resource-schema/dapr-schema/dapr-statestore/snippets/dapr-statestore-recipe.bicep index 0fab757ca..6fc5ac267 100644 --- a/docs/content/reference/resource-schema/dapr-schema/dapr-statestore/snippets/dapr-statestore-recipe.bicep +++ b/docs/content/reference/resource-schema/dapr-schema/dapr-statestore/snippets/dapr-statestore-recipe.bicep @@ -1,9 +1,9 @@ import radius as radius -@description('The app ID of your Radius application. Set automatically by the rad CLI.') +@description('The app ID of your Radius Application. Set automatically by the rad CLI.') param application string -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource myapp 'Applications.Core/containers@2023-10-01-preview' = { diff --git a/docs/content/reference/resource-schema/databases/microsoft-sql/snippets/sql-manual.bicep b/docs/content/reference/resource-schema/databases/microsoft-sql/snippets/sql-manual.bicep index 0dca7d2ca..e9e4ec3a4 100644 --- a/docs/content/reference/resource-schema/databases/microsoft-sql/snippets/sql-manual.bicep +++ b/docs/content/reference/resource-schema/databases/microsoft-sql/snippets/sql-manual.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string param username string param port int diff --git a/docs/content/reference/resource-schema/databases/microsoft-sql/snippets/sql-recipe.bicep b/docs/content/reference/resource-schema/databases/microsoft-sql/snippets/sql-recipe.bicep index 005d293bc..d21031988 100644 --- a/docs/content/reference/resource-schema/databases/microsoft-sql/snippets/sql-recipe.bicep +++ b/docs/content/reference/resource-schema/databases/microsoft-sql/snippets/sql-recipe.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/reference/resource-schema/databases/mongodb/snippets/mongo-manual.bicep b/docs/content/reference/resource-schema/databases/mongodb/snippets/mongo-manual.bicep index eff6c2c33..5aec98987 100644 --- a/docs/content/reference/resource-schema/databases/mongodb/snippets/mongo-manual.bicep +++ b/docs/content/reference/resource-schema/databases/mongodb/snippets/mongo-manual.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource cosmosAccount 'Microsoft.DocumentDB/databaseAccounts@2022-08-15' existing = { diff --git a/docs/content/reference/resource-schema/databases/mongodb/snippets/mongo-recipe.bicep b/docs/content/reference/resource-schema/databases/mongodb/snippets/mongo-recipe.bicep index 10d683222..0ac2b6129 100644 --- a/docs/content/reference/resource-schema/databases/mongodb/snippets/mongo-recipe.bicep +++ b/docs/content/reference/resource-schema/databases/mongodb/snippets/mongo-recipe.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/reference/resource-schema/messaging/rabbitmq/snippets/rabbitmq-manual.bicep b/docs/content/reference/resource-schema/messaging/rabbitmq/snippets/rabbitmq-manual.bicep index 7484a58ea..34047afaa 100644 --- a/docs/content/reference/resource-schema/messaging/rabbitmq/snippets/rabbitmq-manual.bicep +++ b/docs/content/reference/resource-schema/messaging/rabbitmq/snippets/rabbitmq-manual.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/reference/resource-schema/messaging/rabbitmq/snippets/rabbitmq-recipe.bicep b/docs/content/reference/resource-schema/messaging/rabbitmq/snippets/rabbitmq-recipe.bicep index edb8bed3a..523469033 100644 --- a/docs/content/reference/resource-schema/messaging/rabbitmq/snippets/rabbitmq-recipe.bicep +++ b/docs/content/reference/resource-schema/messaging/rabbitmq/snippets/rabbitmq-recipe.bicep @@ -1,6 +1,6 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string resource app 'Applications.Core/applications@2023-10-01-preview' = { diff --git a/docs/content/tutorials/tutorial-dapr/index.md b/docs/content/tutorials/tutorial-dapr/index.md index 35f7720f4..f6746aa1f 100644 --- a/docs/content/tutorials/tutorial-dapr/index.md +++ b/docs/content/tutorials/tutorial-dapr/index.md @@ -20,7 +20,7 @@ For more details on the app and access to the source code, visit the `tutorials/ - [Kubernetes cluster]({{< ref "/guides/operations/kubernetes/overview#supported-clusters" >}}) - [Radius CLI]({{< ref "getting-started" >}}) -- [Radius environment]({{< ref "/guides/deploy-apps/environments/overview" >}}) +- [Radius Environment]({{< ref "/guides/deploy-apps/environments/overview" >}}) - [Dapr installed on your Kubernetes cluster](https://docs.dapr.io/operations/hosting/kubernetes/kubernetes-deploy/) - [Visual Studio Code](https://code.visualstudio.com/) (recommended) - The [Radius VSCode extension]({{< ref "getting-started" >}}) is highly recommended to provide syntax highlighting, completion, and linting @@ -28,7 +28,7 @@ For more details on the app and access to the source code, visit the `tutorials/ ## Step 1: Define the application, `backend` container, and Dapr state store -Begin by creating a new file named `dapr.bicep` with a Radius application that consists of a `backend` container and Dapr state store with Redis: +Begin by creating a new file named `dapr.bicep` with a Radius Application that consists of a `backend` container and Dapr state store with Redis: {{< rad file="snippets/dapr.bicep" embed=true marker="//BACKEND" >}} @@ -107,7 +107,7 @@ In your browser, navigate to the endpoint (e.g. [http://localhost:8080](http://l 1. Press CTRL+C to terminate the `rad run` log console -1. Run `rad app delete` to cleanup your Radius application, containers, and Dapr statestore. The Recipe resources (_Redis container and Dapr component_) are also automatically cleaned up. +1. Run `rad app delete` to cleanup your Radius Application, containers, and Dapr statestore. The Recipe resources (_Redis container and Dapr component_) are also automatically cleaned up. ```bash rad app delete -a dapr diff --git a/docs/content/tutorials/tutorial-recipe/index.md b/docs/content/tutorials/tutorial-recipe/index.md index 1b46bb3bf..7169da5b1 100644 --- a/docs/content/tutorials/tutorial-recipe/index.md +++ b/docs/content/tutorials/tutorial-recipe/index.md @@ -9,7 +9,7 @@ categories: "Tutorial" tags : ["recipes"] --- -This tutorial will teach you the following about recipes +This tutorial will teach you the following about Recipes * How to use “dev” Recipes in your Radius Environment to quickly run with containerized infrastructure. * How to deploy your own Recipes in your Radius Environment to leverage Azure/AWS resources. @@ -35,7 +35,7 @@ Developers don't need to specify what cloud resources they're using in their app - Install the [rad CLI]({{< ref getting-started >}}) - Setup a supported [Kubernetes cluster]({{< ref "guides/operations/kubernetes" >}}) -## Step 1: Initialize a Radius environment +## Step 1: Initialize a Radius Environment 1. Begin in a new directory for your application: @@ -153,7 +153,7 @@ This step requires an Azure subscription or an AWS account to deploy cloud resou ```bash rad resource delete rediscaches db ``` -1. Manually add the Azure cloud provider to your Radius environment +1. Manually add the Azure cloud provider to your Radius Environment Follow the steps [here]({{< ref "howto-azure-provider#manual-configuration" >}}) to add the Azure cloud provider to your existing environment. @@ -230,7 +230,7 @@ This step requires an Azure subscription or an AWS account to deploy cloud resou rad resource delete rediscaches db ``` -1. Manually add the AWS cloud provider to your Radius environment +1. Manually add the AWS cloud provider to your Radius Environment Follow the steps [here]({{< ref "howto-aws-provider#manual-configuration" >}}) to add the AWS cloud provider to your existing environment diff --git a/docs/content/tutorials/tutorial-recipe/snippets/app-aws.bicep b/docs/content/tutorials/tutorial-recipe/snippets/app-aws.bicep index 5091ac9db..f2df05dbf 100644 --- a/docs/content/tutorials/tutorial-recipe/snippets/app-aws.bicep +++ b/docs/content/tutorials/tutorial-recipe/snippets/app-aws.bicep @@ -1,9 +1,9 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string -@description('The ID of your Radius application. Automatically injected by the rad CLI.') +@description('The ID of your Radius Application. Automatically injected by the rad CLI.') param application string //DB diff --git a/docs/content/tutorials/tutorial-recipe/snippets/app-azure.bicep b/docs/content/tutorials/tutorial-recipe/snippets/app-azure.bicep index 4b0d79142..5fa999d14 100644 --- a/docs/content/tutorials/tutorial-recipe/snippets/app-azure.bicep +++ b/docs/content/tutorials/tutorial-recipe/snippets/app-azure.bicep @@ -1,9 +1,9 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string -@description('The ID of your Radius application. Automatically injected by the rad CLI.') +@description('The ID of your Radius Application. Automatically injected by the rad CLI.') param application string //DB diff --git a/docs/content/tutorials/tutorial-recipe/snippets/app.bicep b/docs/content/tutorials/tutorial-recipe/snippets/app.bicep index 63ec11ae3..5fc67ec65 100644 --- a/docs/content/tutorials/tutorial-recipe/snippets/app.bicep +++ b/docs/content/tutorials/tutorial-recipe/snippets/app.bicep @@ -1,9 +1,9 @@ import radius as radius -@description('The ID of your Radius environment. Automatically injected by the rad CLI.') +@description('The ID of your Radius Environment. Automatically injected by the rad CLI.') param environment string -@description('The ID of your Radius application. Automatically injected by the rad CLI.') +@description('The ID of your Radius Application. Automatically injected by the rad CLI.') param application string resource frontend 'Applications.Core/containers@2023-10-01-preview' = { diff --git a/docs/shared-content/installation/install-radius/initialize-radius.md b/docs/shared-content/installation/install-radius/initialize-radius.md index f09f7b7f5..76fe415be 100644 --- a/docs/shared-content/installation/install-radius/initialize-radius.md +++ b/docs/shared-content/installation/install-radius/initialize-radius.md @@ -1,6 +1,6 @@ The Radius control-plane is a set of services that provide the core functionality of Radius. It is deployed as a set of containers in a Kubernetes cluster. -1. Initialize a new [Radius environment]({{< ref "/guides/deploy-apps/environments/overview">}}) with [`rad init`]({{< ref rad_init >}}): +1. Initialize a new [Radius Environment]({{< ref "/guides/deploy-apps/environments/overview">}}) with [`rad init`]({{< ref rad_init >}}): ```bash rad init ```