Azure Insights: Resource locks; Rightsizing resources; Private AKS cluster access

Azure pros discuss resource locks, rightsizing resources, and accessing a private AKS cluster over VPN.

How to maintain access to Terraform when using Azure resource locks

Daniel Neumann, writing on Daniel’s Tech Blog, explained that Azure resource locks are an essential to protecting against accidental deletion and modification. Resources in Azure inherit a resource lock from the parent resource. As a result, most resource locks are inherited from the resource or the resource group. This can limit the ability to use Terraform because delete operations are blocked. He wrote:

The solution is quite simple: moving the resource lock down the inheritance chain to the end. Instead of putting the resource lock on the resource group or parent resource level, we set it on the child resource.

At first glance, this fix doesn’t seem very intuitive. According to Neumann, this setup works because before a resource group and its child resources are deleted, the system checks for a resource lock and cancels the deletion if a resource lock exists. Neumann demonstrated how to modify code accordingly to get the most out of Terraform while maintaining resource locks.

Achieving Azure rightsizing

Writing on the Serverless360 blog, Ranjith Eswaran discussed how to “rightsize” Azure resources. Customers can rightsize Azure by carefully analyzing under- and overutilization of resources. The process begins by identifying relevant resources and understanding how their utilization might vary.