273: Phi-fi-fo-fum, I Smell the Bones of The Cloud Pod Hosts

Welcome to episode 273 of The Cloud Pod, where the forecast is always cloudy! Hold onto your butts – this week your hosts Justin, Ryan, Matthew and (eventually) Jonathan are bringing you two weeks worth of cloud and AI news. We’ve got Karpenter, Kubernetes, and Secrets, plus news from OpenAI, MFA changes that are going to be super fun for Matthew, and Azure Phi. Get comfy – it’s going to be a doozy!

Titles we almost went with this week:

• The Cloud Pod Teaches Azure-normalized Camel Casing
• The Cloud Pod Travels to Malaysia
• Azure Detaches Itself From its Own Scale Sets
• The Cloud Pod Conditionally Writes Show Notes 
• You got MFA!
• The Cloud Pod Delays Deleting Itself
• The Cloud Pod is Now the Cloud Pod Podcast!

A big thanks to this week’s sponsor:

We’re sponsorless! Want to get your brand, company, or service in front of a very enthusiastic group of cloud news seekers? You’ve come to the right place! Send us an email or hit us up on our slack channel for more info. 

General News

01:37 Terraform AzureRM provider 4.0 adds provider-defined functions 

• Terraform is announcing the GA of Terraform AzureRM provider 4.0.  The new version improves the extensibility and flexibility in the provider. 
• Since the Providers’ Last major release in March 2022, Hashi has added support for some 340 resources and 120 data sources, bringing the total Azure resources to 1,101 resources and almost 360 data sources. 
• The provider has topped 660M downloads, MS and Hashi continue to develop new, innovative integrations that further ease the cloud adoption journey to enterprise organizations. 
• With Terraform 1.8, providers can implement custom functions that you can call from the Terraform configuration. The new provider adds two Azure-specific provider functions to let users correct the casing of their resource IDs or access the individual components of it. 
• Previously, the Azure RM provider took an all-or-nothing approach to Azure resource provider registration, where the Terraform provider would either attempt to register a fixed set of 68 providers upon initialization or registration or be skipped. 
• This didn’t match Microsoft’s recommendations, which are to register resource providers only as needed, and to enable the services you’re actively using. 
• With adding two new feature flags, resource_provider_registrations and resource_providers_to_register, users now have more control over which providers to register automatically or whether to continue managing a subscription resources provider. 
• AzureRM has removed a number of deprecated items, and it is recommended that you look at the removed resources/data sources and the