Radius v0.61.1
This patch fixes an issue where the deployment engine created Kubernetes resources even when their Bicep conditions evaluated to false, causing unwanted resources such as HorizontalPodAutoscalers to remain in the cluster after rad app delete completed successfully. Check out the changelog for more details of what was addressed in this patch.
Changelog
- Honor Bicep conditions for Kubernetes resources and other resources handled through extensibility providers. Resources whose conditions evaluate to
falseare now skipped without invoking their providers, while dependent resources can continue deploying. This prevents unwanted, untracked resources from being created and left behind after application deletion.