Azure Extended Zones are small-footprint extensions of Azure placed in metros, industry centers, or a specific jurisdiction to serve low-latency and data-residency workloads. Azure Extended Zones supports virtual machines (VMs), containers, storage, and a selected set of Azure services and can run latency-sensitive and throughput-intensive applications close to end users and within approved data residency boundaries.

Recently announced Azure Extended Zones in Perth, Australia, provide a new option for customers to run their workloads (make note only a subset of resources are compatible) closer to home.

This is particularly beneficial for industries that require low latency and data residency, such as finance, healthcare, and government.

Today, we will look at deploying Kubernetes AI Toolchain Operator (KAITO) straight from Visual Studio Code.

Today, we will look at KubeBuddy.

The tag line of KubeBuddy is:

Kubernetes says your cluster is healthy. It’s probably not.

Today, we are going to look at Codespace Secrets.

Last year, I blogged about Container Patching with Azure DevOps, Trivy and Copacetic, and how to use Azure DevOps to automate the patching of your container images using Trivy and Copacetic. This was a great solution, but it required a lot of manual work to set up and maintain. Today, I am going to take a look at Continuous Patching with Azure Container Registry (ACR) and how to use it to automate the patching of your container images.