rad upgrade kubernetes CLI reference
rad upgrade kubernetes
Upgrades Radius on a Kubernetes cluster
Synopsis
Upgrade Radius in a Kubernetes cluster using the Radius Helm chart. This command upgrades the Radius control plane in the cluster associated with the active workspace. To upgrade Radius in a different cluster, switch to the appropriate workspace first using ‘rad workspace switch’.
By default, the upgrade preserves any values that were previously set on the existing Helm release. This means non-default settings configured during install or earlier upgrades (for example ‘global.azureWorkloadIdentity.enabled=true’ or ‘database.enabled=true’) are carried forward automatically — the upgrade starts from the new chart’s defaults, re-applies the previously stored user-supplied values, and then overlays any –set / –set-file values provided in the current invocation. Pass –reset-values to opt out and use only the current –set flags plus the new chart’s defaults (this mirrors ‘helm upgrade –reset-values’).
Warning: Radius RBAC is a work in progress. Full functionality is not guaranteed. The ‘global.rbac.enabled’ and ‘global.rbac.dryRun’ Helm settings are experimental, including when their values are preserved from a previous installation. Do not rely on RBAC for production access control.
When Contour is installed, the upgrade also upgrades it. Contour chart values can be set with ‘–contour-set’ and ‘–contour-set-file’. They take precedence over the values stored on the Contour release and over the values that Radius sets, and –reset-values discards the stored Contour values too. Before it upgrades anything, Radius checks that the Contour upgrade does not delete CRDs or take over Gateway API CRDs that belong to something else, and that Contour can use the Gateway API CRDs in the cluster.
The upgrade process includes preflight checks to ensure the cluster is ready for upgrade. Preflight checks include:
- Kubernetes connectivity and permissions
- Helm connectivity and Radius installation status
- Version compatibility validation
- Cluster resource availability
- Custom configuration parameter validation
- Contour upgrade validation, with the same Contour values as the upgrade
Radius is installed in the ‘radius-system’ namespace. For more information visit https://docs.radapp.io/concepts/technical/architecture/.
rad upgrade kubernetes [flags]
Examples
# Upgrade Radius in the cluster of the active workspace
rad upgrade kubernetes
# Check which workspace is active
rad workspace show
# Switch to a different workspace before upgrading
rad workspace switch myworkspace
rad upgrade kubernetes
# Upgrade Radius with custom configuration
rad upgrade kubernetes --set key=value
# Upgrade Radius with a custom container registry
# Images will be pulled as: myregistry.azurecr.io/controller, myregistry.azurecr.io/ucpd, etc.
rad upgrade kubernetes --set global.imageRegistry=myregistry.azurecr.io
# Upgrade Radius to a specific version tag for all components
rad upgrade kubernetes --set global.imageTag=0.48
# Upgrade Radius with custom registry and tag
# Images will be pulled as: myregistry.azurecr.io/controller:0.48, etc.
rad upgrade kubernetes --set global.imageRegistry=myregistry.azurecr.io,global.imageTag=0.48
# Upgrade Radius with private registry and image pull secrets
# Note: Secret must be created in radius-system namespace first
rad upgrade kubernetes --set global.imageRegistry=myregistry.azurecr.io --set 'global.imagePullSecrets[0].name=regcred'
# Upgrade Radius with multiple image pull secrets for different registries
rad upgrade kubernetes --set 'global.imagePullSecrets[0].name=azure-cred' \
--set 'global.imagePullSecrets[1].name=aws-cred'
# Upgrade to a specific version
rad upgrade kubernetes --version 0.47.0
# Upgrade to the latest available version
rad upgrade kubernetes --version latest
# Upgrade Radius with values from a file
rad upgrade kubernetes --set-file global.rootCA.cert=/path/to/rootCA.crt
# Skip preflight checks (not recommended)
rad upgrade kubernetes --skip-preflight
# Run only preflight checks without upgrading
rad upgrade kubernetes --preflight-only
# Upgrade Radius using a Helm chart from specified file path
rad upgrade kubernetes --chart /root/radius/deploy/Chart
# Discard previously-stored Helm values and upgrade using only the current --set flags
# plus the new chart's defaults (mirrors 'helm upgrade --reset-values').
rad upgrade kubernetes --reset-values
# Upgrade Radius and Contour on a k3s cluster with Traefik, whose Gateway API CRDs lack TLSRoute,
# TCPRoute, and BackendTLSPolicy v1alpha3, by turning off the Contour features that use them
rad upgrade kubernetes --contour-set "contour.extraArgs={--disable-feature=tlsroutes,--disable-feature=tcproutes,--disable-feature=backendtlspolicies}"
Options
--chart string Specify a file path to a helm chart to upgrade Radius from
--contour-set stringArray Set Contour chart values on the command line when Contour is installed (can specify multiple or separate values with commas: key1=val1,key2=val2)
--contour-set-file stringArray Set Contour chart values from files on the command line when Contour is installed (can specify multiple or separate files with commas: key1=filename1,key2=filename2)
-h, --help[=true|false] help for kubernetes
--kubecontext string The Kubernetes context to use, will use the default if unset
--preflight-only[=true|false] Run only preflight checks without performing the upgrade
--reset-values[=true|false] Discard values previously stored on the Helm releases and use only the current --set / --set-file and --contour-set / --contour-set-file flags plus the new charts' defaults
--set stringArray Set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
--set-file stringArray Set values from files on the command line (can specify multiple or separate files with commas: key1=filename1,key2=filename2)
--skip-preflight[=true|false] Skip preflight checks before upgrade (not recommended)
--version string Specify the version to upgrade to (default: CLI version, use 'latest' for latest available)
Options inherited from parent commands
--config string config file (default "$HOME/.rad/config.yaml")
-o, --output string output format (supported formats are json, table) (default "table")
SEE ALSO
- rad upgrade - Upgrades Radius for a given platform
Feedback
Was this page helpful?
Glad to hear it! Please feel free to star our repo and join our Discord server to stay up to date with the project.
Sorry to hear that. Please tell us how we can improve.