Tag: Infrastructure as Code
-
How to not block Terraform with Azure resource locks
Azure resource locks are an essential building block protecting Azure resources from accidental deletion or modifications. In today’s blog post, I show you how to use Azure resource locks to protect your Azure resources and how to not block your Terraform infrastructure as code processes. Common setup and the Terraform issue Resources in Azure inherit…
-
Azure Kubernetes Service – Using Kubernetes credential plugin kubelogin with Terraform
In today’s blog post we have a look at the Kubernetes credential plugin kubelogin for Azure Kubernetes Service and how to use it with Terraform. -> https://github.com/Azure/kubelogin -> https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins The Azure Kubernetes Service cluster I am using for demonstration is an AKS-managed Azure Active Directory one with local accounts disabled. Disabling the local accounts turns…
-
Apply configuration changes to the default node pool in AKS via Bicep
In today’s blog post we look into the Bicep and how to apply configuration changes to the default node pool in Azure Kubernetes Service within the same Bicep template. What sounds easy on the first look gets nasty if all the things shall be done within the same template like creating an Azure Kubernetes Service…
-
How to change the node size of the default node pool in AKS without downtime?
Currently, as of writing this blog post, Azure Kubernetes Service does not support changing the node size of the default node pool or additional node pools without recreating the whole AKS cluster or the additional node pool. Having all the configuration in infrastructure as code whether it is Bicep or Terraform seems to be a…
-
Conditions with for_each in Terraform
Conditions in Terraform are well-known and can provide in combination with the for_each argument a lot of flexibility. In today’s blog post I walk you through an example storage module I have created to showcase the topic. The module consists of three resources a resource group, a lock, and a storage account. As I am…
-
Unix time format in Azure Resource Manager templates
The Unix time format is represented in seconds elapsed since 01.01.1970 UTC. So, it is different from the standard time format we are used to. Depending on the Azure service some attributes in the Azure API / ARM template require the Unix time format especially Azure Key Vault keys and secrets. Those ones have two…