Skip to content

Conversation

@Reshrahim
Copy link
Contributor

Thank you for helping make the Radius documentation better!

Please follow this checklist before submitting:

  • Read the contribution guide
  • Commands include options for Linux, MacOS, and Windows within codetabs
  • New file and folder names are globally unique
  • Page references use shortcodes instead of markdown or URL links
  • Images use HTML style and have alternative text
  • Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:

Description

Issue reference

Signed-off-by: Reshma Abdul Rahim <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>
@Reshrahim Reshrahim requested review from a team as code owners October 23, 2025 21:14
@Reshrahim Reshrahim changed the base branch from v0.52 to edge October 23, 2025 21:15
Signed-off-by: Reshma Abdul Rahim <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>

- **Dashboard** – The Backstage based UI for managing Radius resources. You can disable it during installation.

- **Bicep extensions** – Radius packages Resource Type definitions as Bicep extensions stored in OCI registries or a file share. To use the Resource Types in your application, a workstation or CI runner must have config file (`bicepconfig.json`) that points to the extensions. Checkout the [how-to generate Bicep extensions](TODO) for more information.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@willdavsmith may have more information here

---
type: docs
title: "Helm Installation Options"
linkTitle: "Helm Installation"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need Helm Upgrade page?

Copy link
Contributor Author

@Reshrahim Reshrahim Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a separate Helm Upgrade page but will be part of the upgrade page under Installation.

This is a reference page for Helm configuration options. Do we have specific upgrade related options?

Signed-off-by: Reshma Abdul Rahim <[email protected]>
Reshrahim and others added 2 commits November 21, 2025 14:45
Signed-off-by: Reshma Abdul Rahim <[email protected]>
Updated prerequisites for Azure Container Instances guide to reflect changes in Radius installation and Kubernetes requirements.

Signed-off-by: Reshma Abdul Rahim <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>
Copy link
Collaborator

@zachcasper zachcasper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only reviewed through "Deploy to Air-gapped environments". Will review again when complete.


- **Observability back ends** – Prometheus and Zipkin/Jaeger endpoints collect metrics and traces using the chart settings. Checkout the [Observability guide](TODO) for more information.

## Installation Requirements
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only requirements I see here are:

  • Kubernetes 1.23.8 and higher
  • cluster-admin permissions in order to install Radius

Comment on lines +3 to +8
title: "How-To: Install Radius on Kubernetes"
linkTitle: "Install"
description: "Learn how to install Radius on Kubernetes"
weight: 100
categories: "How-To"
tags: ["Kubernetes"]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: "How-To: Install Radius on Kubernetes"
linkTitle: "Install"
description: "Learn how to install Radius on Kubernetes"
weight: 100
categories: "How-To"
tags: ["Kubernetes"]
title: "How-To: Install Radius"
linkTitle: "Install"
description: "Learn how to install Radius on Kubernetes"
weight: 100

Comment on lines +107 to +112
#### Deploy to Air-gapped environments

Radius pulls container images for control plane services from the GitHub Container Registry (ghcr.io). In environments with strict security controls or no internet access (air‑gapped), mirror the required images to an internal registry and configure Radius to use that registry.

Example of mirroring images (requires access to both registries):

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#### Deploy to Air-gapped environments
Radius pulls container images for control plane services from the GitHub Container Registry (ghcr.io). In environments with strict security controls or no internet access (air‑gapped), mirror the required images to an internal registry and configure Radius to use that registry.
Example of mirroring images (requires access to both registries):
#### Installing Radius in air-gapped environments
The default Radius installation references container images stored in GitHub Container Registry (ghcr.io). In environments without direct access to ghci.io, the container images must be manually pulled and stored in a local OCI registry. For example, the script below pulls from ghcr.io and pushes the images to an internal OCI registry:


SOURCE_REGISTRY="ghcr.io/radius-project"
TARGET_REGISTRY="myregistry.azurecr.io"
VERSION="latest" # or specific version like "0.48"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
VERSION="latest" # or specific version like "0.48"
VERSION="0.53" # or other specific version

)

SOURCE_REGISTRY="ghcr.io/radius-project"
TARGET_REGISTRY="myregistry.azurecr.io"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
TARGET_REGISTRY="myregistry.azurecr.io"
TARGET_REGISTRY="<internal-oci-registry-hostname>"

Comment on lines +136 to +142
Then install Radius configured to pull images from your private registry, and supply image pull secrets if authentication is required.

```bash
rad install kubernetes \
--set global.imageRegistry=myregistry.azurecr.io \
--set global.imageTag={{ .Chart.AppVersion }} \
--set global.imagePullSecrets[0].name=myregistry-secret
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Then install Radius configured to pull images from your private registry, and supply image pull secrets if authentication is required.
```bash
rad install kubernetes \
--set global.imageRegistry=myregistry.azurecr.io \
--set global.imageTag={{ .Chart.AppVersion }} \
--set global.imagePullSecrets[0].name=myregistry-secret
Then use the `global.imageRegistry` and `global.imageTag` installation options when installing Radius.
```bash
rad install kubernetes \
--set global.imageRegistry=<internal-oci-registry-hostname> \
--set global.imageTag=0.53

--set global.imagePullSecrets[0].name=myregistry-secret
```

When using a custom registry, images are pulled directly from <registry>/<image-name>:<tag> format. For example, with myregistry.azurecr.io, the controller image will be pulled from myregistry.azurecr.io/controller:latest.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When using a custom registry, images are pulled directly from <registry>/<image-name>:<tag> format. For example, with myregistry.azurecr.io, the controller image will be pulled from myregistry.azurecr.io/controller:latest.

Replace this with instructions on using --set global.imagePullSecrets[0].name=myregistry-secret. But I don't know why this would be required. I would expect Kubernetes to already be configured for this https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

Co-authored-by: Zach Casper <[email protected]>
Signed-off-by: Reshma Abdul Rahim <[email protected]>
@github-actions
Copy link

github-actions bot commented Dec 3, 2025

❌ Spellcheck Failed

There are spelling errors in your PR. Visit the workflow output to see what words are failing.

Adding new words

If you are adding a new custom word refer to the docs guide

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants