// Content

Chris is joined by Karl Cooke (IrishTechie) for a live deep-dive into the GitHub Actions workflows powering CloudWithChris.com. They explore why GitHub was chosen over Azure DevOps, walk through a real-world CI/CD pipeline for a Hugo static site deployed to Azure Blob Storage with CDN purging, and examine how to manage secrets and approvals using GitHub Environments. The session also covers linting Markdown with GitHub Super Linter, early thinking on Playwright-based UI tests, the security considerations around third-party actions from the marketplace, and building a custom .NET GitHub Action for content cross-posting.

Chris rounds up the week's Azure, Azure DevOps, and GitHub news — including the rebrand of Windows Virtual Desktop to Azure Virtual Desktop, Azure FHIR healthcare API updates, SAP on Azure, and a preview of the Azure Arc hybrid and multi-cloud digital event. On the GitHub side, supply chain security takes the spotlight with package registry credential scanning, Dependabot enhancements, and GitHub's Blacktocat fifth anniversary celebrating Black voices in tech. Cloud with Chris recaps include Carl Cook on GitHub Actions, Azure Arc for apps (Event Grid), Sarah Lean on hybrid cloud and DevRel life, and Will Esprit demonstrating the Geode pattern hands-on.

Setting up an Azure API Management Gateway on Azure Arc In part 1 of this Using Azure Arc for Apps series, we explored Azure Arc and Azure Arc enabled …

App Service Kubernetes Environment In part 1 of this Using Azure Arc for Apps series, we explored Azure Arc and Azure Arc enabled Kubernetes clusters. In part …

Mental health and career development are more closely intertwined than people often appreciate. Chris and long-time colleague Glenn Small (Analytics Manager at AWS) share personal experiences of burnout, severe anxiety, and pandemic isolation — and draw out practical lessons for setting expectations, building healthy boundaries at work, and knowing when to ask for help.

In part 1 of this Using Azure Arc for Apps series, we explored Azure Arc and Azure Arc enabled Kubernetes clusters. In part 2, we deployed an App Service Kubernetes Environment into our Azure Arc enabled Kubernetes cluster. As you'll likely be aware, both Azure Functions (this blog post) and Azure Logic Apps (the next blog post) can run on Azure App Service. The same is true of an App Service Kubernetes Environment, we can run App Services, Logic Apps and Azure Functions.

Join me and a few colleagues as we talk about demos during presentations and whether they should be live demos or recorded and the arguments for and against each option.

The COVID-19 pandemic forced game studios worldwide to rethink how developers, artists, designers, and audio engineers collaborate remotely on titles with massive file sizes and unforgiving release schedules. In this episode of Cloud Gaming Notes, Chris is joined by Lee Williams to explore how the gaming industry adapted using cloud services — from cloud-hosted design environments and Azure infrastructure to source control workflows with GitHub and Azure DevOps, video collaboration tooling, and the emerging paradigm of building entire games in the cloud. They also touch on how live game streaming is creating an entirely new entertainment industry built on the same cloud foundations.

In part 1 of this Using Azure Arc for Apps series, we explored Azure Arc and Azure Arc enabled Kubernetes clusters. In this post, we'll be exploring App Services on Azure Arc. More specifically, these application services run on an Azure Arc enabled Kubernetes cluster, which is a pre-requisite for us to progress. At time of writing, this approach is in public preview, so we may see certain limitations / features that are not yet available.

At Microsoft //Build 2021, Microsoft announced a series of updates relating to Cloud Native Applications anywhere. In summary, those updates refer to running Azure Services (such as App Services, Logic Apps, Azure Functions, Event Grid and API Management) in any Kubernetes cluster which is managed by Azure Arc. That means you could have Azure App Services running in Amazon Web Services (AWS), Google Cloud Platform (GCP), or in your on-premises Kubernetes deployment. This is a significant update, so I've decided that I'll be writing a series of blog posts on the topic - as one post would not do the topic justice!