Retrying Bicep Resource Deployments with the @retryOn Decorator
Use Bicep’s @retryOn decorator to retry resource deployments for selected transient Azure errors, with a practical role assignment example and the limits to keep in mind.
Use Bicep’s @retryOn decorator to retry resource deployments for selected transient Azure errors, with a practical role assignment example and the limits to keep in mind.
While evaluating a move from the cluster autoscaler to Node Auto Provisioning (NAP) on AKS, no nodes were created. NAP quietly fell back from ephemeral OS disks to managed disks, and our Azure Policy denied them.
What AKS desktop actually does — Projects, guided deployments without YAML, a natural-language AI troubleshooting assistant, and a built-in plugin catalog — walked through as a demo you can reproduce on your own cluster.
A real-world look at SQL error 9001 in Azure SQL diagnostic logs — what it means, why it happens during planned maintenance reconfigurations, and how to make your application resilient against it.
An AKS incident from our deployment pipeline: Azure Monitor addons moved to a cluster extension-based backend — and a sensible Azure Policy that blocked extensions suddenly broke our AKS provisioning with no warning.
A real incident from our AKS platform: resource locks on AKS-managed Azure disks silently broke the CSI driver during a node drain, leaving pods stuck without volumes. Here's what went wrong and what we should have done instead.
A real-world story: how a nightly cleanup pipeline got blocked by a namespace stuck in Terminating, and the kubectl proxy + finalizer trick that finally got it unstuck.