Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added small blurb on storing env variables as secrets for connections. #1042

Merged
merged 11 commits into from
Mar 4, 2024
Merged
Show file tree
Hide file tree
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ Refer to the probes section of the [container resource schema]({{< ref "containe

## Connections

jasonviviano marked this conversation as resolved.
Show resolved Hide resolved
When a connection between two resources is declared, Radius injects resource related information into environment variables that are then used to access the respective resource without having to hard code URIs, connection strings, access keys, or anything that application code needs to successfully communicate.
When a connection between two resources is declared, Radius injects resource related information into environment variables that are then used to access the respective resource without having to hard code URIs, connection strings, access keys, or anything that application code needs to successfully and securely communicate, which is done by storing these environment variables safely inside of the Radius Environment.

These environment variables follow a naming convention that makes their use predictable. The naming pattern is derived from the connection name and resource type, which determines what values are required. This way the code that needs to read the values gets to define how they are named. Refer to the [reference documentation]({{< ref resource-schema >}}) of each resource for more information.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Kubernetes version `1.23.8` or higher is recommended to run Radius.

## Resource mapping

Radius resources, when deployed to a Kubernetes environment, are mapped to one or more Kubernetes objects. The following table describes the mapping between Radius resources and Kubernetes objects:
Radius resources, when deployed to a Kubernetes environment, are mapped to one or more Kubernetes objects.If a connection is established between Radius resources they are stored as Secret objects if they are Radius automatically-configured values and regular Kubernetes objects if they are manually configured by a user. The following table describes the mapping between Radius resources and Kubernetes objects:
jasonviviano marked this conversation as resolved.
Show resolved Hide resolved

| Radius resource | Kubernetes object |
|----------------------------------|-------------------|
Expand Down
Loading