RSS

Announcing Radius v0.51.0

By Radius Team |

Today, we’re excited to announce the release of Radius v0.51.0! This update introduces several enhancements to improve usability, streamline workflows, and address key user concerns. Whether you’re a developer or platform engineer, this release brings meaningful updates to help you manage your cloud-native Applications more effectively. You can find the full release notes here.

If you’re new to Radius, visit radapp.io to learn more about the platform and its capabilities. To get started, check out the getting started guide for step-by-step instructions on installing Radius and deploying your first application.

Purge behavior updated for uninstall command

Radius v0.51.0 introduces an update to the --purge flag for the rad uninstall kubernetes command. When this flag is specified, all Kubernetes resources created by Radius—including resources generated during application deployments—will now be deleted. This enhancement ensures a more thorough cleanup process when uninstalling Radius from your Kubernetes environment. For detailed usage instructions, refer to the CLI documentation.

Progress status feedback added to application deletion command

The rad app delete command has been improved to provide real-time progress status and a confirmation summary during application deletion. This update addresses a common usability issue where longer deletion operations could appear unresponsive. With this enhancement, you’ll now have clear visibility into the deletion process, ensuring a smoother experience. Learn more about this feature in the CLI documentation.

ACI deployments now use dynamic resource group location

Radius has updated its Azure Container Instances (ACI) deployment process to dynamically retrieve and use the resource group’s location. Previously, deployments defaulted to the hardcoded West US 3 region due to early support for ACI NGroups. This improvement ensures that Radius adapts to your resource group’s location, simplifying ACI Environment creation and resource deployment. For more information, see the how-to guide.

Contour ingress controller installation disabled

Radius v0.51.0 disables the automatic installation of the Contour ingress controller during rad install kubernetes and rad init. This change is due to Bitnami’s deprecation of their public container registry, which impacts the availability of Contour images.

If your Applications rely on Radius Gateway resources for ingress functionality, you’ll need to manually install and configure a Contour ingress controller before deploying Gateway resources. For installation guidance, consult the Contour documentation. Additionally, you may find helpful insights in the Contour community discussion.

This change is temporary while Radius evaluates alternative ingress controller options and repository sources.

Upgrading to Radius v0.51.0

To upgrade to Radius v0.51.0, first update your Radius CLI, then run rad upgrade kubernetes. Note that only incremental version upgrades are supported. For detailed upgrade instructions, consult the upgrade documentation.

Learn More and Get Involved

We would love for you to join us to help build Radius: