Links: 202306261006 https://www.youtube.com/watch?v=7VQ7BZwuZkU https://cloudblogs.microsoft.com/quantum/2023/06/21/microsoft-achieves-first-milestone-towards-a-quantum-supercomputer/
Did a refactor of some of our Bicep template code for our AKS clusters today. Before, we were using a rather complicated line of code using string interpolation. var vnetSubnetId = '${resourceId(vnetResourceGroupName, 'Microsoft.Network/virtualNetworks', vnetName)}/subnets/${vnetSubnetName}' This was hard to read and the Bicep linter gave the following warning in my editor and during deployment: WARNING: D:\a\1\a\drop\Generic-templates\containers\azure-kubernetes-service\v4.0\templates\aks.bicep(117,7) : Warning use-resource-id-functions: If property “vnetSubnetID” represents a resource ID, it must use a symbolic resource reference, be a parameter or start with one of these functions: extensionResourceId, guid, if, reference, resourceId, subscription, subscriptionResourceId, tenantResourceId. Found nonconforming expression at vnetSubnetID -> vnetSubnetId [https://aka.ms/bicep/linter/use-resource-id-functions] ...
CNI? CNI stands for Container Network Interface. It allows communication between pods and services. Current Azure CNI limitations Let’s take a practical example. We have an enterprise environment where a large network is utilized, spanning multiple clouds and on-prem infrastructure hubs. To enable seamless communication across these sections, they must belong to the same network. As a result, specific IP address ranges are assigned to each section, with AWS, On-Prem A, and Azure each having their respective ranges. ...
Not sure how this will play out with more complex applications, but I can definitely see how this would accellerate the process for developers to get their first versions deployed without the toil of setting up manifests and pipelines. Will definitely play around with this soon and I’m curious to see how far Microsoft will take this! Links: 202306092006 ...
It’s now possible to abort long running operations on AKS clusters. It was released as Generally Available. For example: az aks operation-abort --name myAKSCluster --resource-group myResourceGroup Links: 202304270704 https://azure.microsoft.com/en-us/updates/generally-available-operation-abort-in-aks/ https://learn.microsoft.com/en-us/azure/aks/manage-abort-operations?tabs=azure-cli
Deploying to subscriptions and management groups To tell Bicep which scope to deploy to, use the targetScope keyword, for example, managementGroup. You’re not specifying which management group exactly, this is done during deployment of the template file. targetScope can be set to resourceGroup, subscription, managementGroup or tenant. If it is not set, Bicep assumes resourceGroup. create a resource group targetScope = 'subscription' resource resourceGroup 'Microsoft.Resources/resourceGroups@2021-01-01' = { name: 'example-resource-group' location: 'westus' } To deploy you use az deployment group create for resource groups, but you use az deployment sub create for subscriptions, mg for management group and tenant for tenant. ...
Today I finished the Intermediate Bicep module. Here are my notes. Child and Extension You can also use Bicep to refer to resources that were created outside the Bicep file itself. For example, you can refer to resources that your colleagues have created manually by using the Azure portal, or from within another Bicep template or module, even if they’re in a different resource group or subscription. By using these features of Bicep, you can unlock the ability to create powerful templates that deploy all aspects of your Azure infrastructure. ...
I’ll be working with Bicep during my next contract, so I’m working through the Bicep modules on Microsoft Learn to prepare. I must say that these modules are particularly helpful. They are well structured and they provide you with free sandbox environments to practice deploying the templates you create. Why Bicep? Resources in Azure are deployed by the Azure Resource Manager (ARM). These resources are JSON objects under the covers, and ARM templates are a way to generate these JSON objects. However, JSON is not really meant to be edited by humans, and the ARM templates are not very suitable for editing either. Thus, Bicep was developed to allow for a better editing experience and better readability and reusability. ...
I’m typing this 30 minutes after I passed my AZ-400 exam. I’m sitting in a lovely cafe on Leidseplein in Amsterdam and feel relieved. Another significant certification bites the dust. This one took about 70 hours of study. I started preparing immediately after passing my AZ-104 exam, which was a good move. The AZ-400 requires you to know many details about Azure services and how to access them. For example, Shared Access Signatures are only used for accessing storage accounts, but they came up quite often as alternative answers to the questions. ...
The PAT (Personal Access Token) often comes up during practice tests for the AZ-400. One way to remember when to use a PAT is that these are only for authenticating into Azure DevOps, never to external services. For example, you might get a question on connecting your Azure DevOps project with a GitHub account from Azure DevOps, and PAT will show up as one of the alternative answers. By remembering that PATs are only for authenticating into ADO, you can elminate this alternative, and make your choice easier. ...