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.
Practical guides and insights on cloud infrastructure, DevOps, and modern engineering practices.
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.
Our AKS NAP evaluation showed a trade-off between consolidation and daily financial calculations inside Deployment pods. Here is why we kept CAS for now.
A Terraform demo for enabling AKS control plane metrics, tuning Prometheus collection, and exploring API server and etcd dashboards in Azure Managed Grafana.
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.
Configure push-based Harbor replication to Azure Container Registry using a repository-scoped ACR token, resource filters, and event-based triggers.