Advanced Container Apps Networking: VNet Integration and Centralized Firewall Traffic Logging
Azure community, I recently documented a networking scenario relevant to Azure Container Apps environments where you need to control and inspect application traffic using a third-party network virtual appliance. The article walks through a practical deployment pattern: • Integrate your Azure Container Apps environment with a Virtual Network. • Configure user-defined routes (UDRs) so that traffic from your container workloads is directed toward a firewall appliance before reaching external networks or backend services. • Verify actual traffic paths using firewall logs to confirm that routing policies are effective. This pattern is helpful for organizations that must enforce advanced filtering, logging, or compliance checks on container egress/ingress traffic, going beyond what native Azure networking controls provide. It also complements Azure Firewall and NSG controls by introducing a dedicated next-generation firewall within your VNet. If you’re working with network control, security perimeters, or hybrid network architectures involving containerized workloads on Azure, you might find it useful. Read the full article on my blog
Trying to deploy container app from GitHub Actions - Authentication failure
I am trying to deploy to an Azure Container App from GitHub Actions. I am following this guide: https://learn.microsoft.com/en-us/azure/container-apps/github-actions#build-and-deploy-to-container-apps Here is this step: deploy-to-container-apps: permissions: contents: none runs-on: ubuntu-latest needs: build-push-container-image steps: - uses: azure/login@v1 with: creds: ${{ secrets.AZURE_CREDENTIALS }} - name: Build and deploy Container App uses: azure/container-apps-deploy-action@v1 with: registryUrl: ghcr.io imageToDeploy: ghcr.io/${{ env.IMAGE_NAME }}:${{ github.run_number }} targetPort: 3500 ingress: external containerAppName: ${{ env.CONTAINERAPPS_APP }} containerAppEnvironment: ${{ env.CONTAINERAPPS_ENVIRONMENT }} resourceGroup: ${{ env.RESOURCE_GROUP }} I use this command to create an rbac: az ad sp create-for-rbac -n "spn-aca-github" --role Contributor --scope /subscriptions/$SUBSCRIPTION_ID --sdk-auth I then add the output of this command as a secret: When I run the flow, I get this error: Run az containerapp show \ Run CA_GH_ACTION_CONTAINER_APP_ENVIRONMENT="aca-environment" Run CA_GH_ACTION_INGRESS_ENABLED="true" Run CA_GH_ACTION_TARGET_PORT="3500" Run CA_GH_ACTION_TARGET_PORT_ARG="--target-port 3500" Run CA_GH_ACTION_USE_UP="true" Run az containerapp up \ WARNING: Using resource group 'rg-containerapps-github-actions' WARNING: Using ContainerAppEnvironment 'aca-environment' in resource group rg-containerapps-github-actions WARNING: Updating Containerapp album-backend-api in resource group rg-containerapps-github-actions ERROR: (InvalidParameterValueInContainerTemplate) The following field(s) are either invalid or missing. Field 'template.containers.album-backend-api.image' is invalid with details: 'Invalid value: "ghcr.io/adamcodes716/containerapps-album-api:3": GET https:?scope=repository%3Aadamcodes716%2Fcontainerapps-album-api%3Apull&service=ghcr.io: UNAUTHORIZED: authentication required';. Error: Process completed with exit code 1. Any idea as to what the issue might be?Azure decommissioning - December 2023
Hi there I know that 2023 is over, but if you missed them, here are the decommissions announced by the Azure teams during the month of December: 1). 5G & Space Azure Object Anchors The service will be withdrawn on May 20, 2024. So for those like me, who don't know this service, it allows you to create 3D content objects through virtual points on physical objects. Azure Spatial Anchors Same punishment for the Azure Spatial Anchors service which will be withdrawn on November 20, 2024. Just like the previous one, I didn't know it, and it allows developers to generate mixed reality applications. -- 2). Containers Azure Container Apps On the Azure Container Apps side, the product team has decided to remove the plane 2023-04-01-preview control API from March 6, 2024. You simply need to switch to the latest stable version of the API i.e. 2023-05-01 Azure Kubernetes Service On the AKS side, the Pod Security Policy functionality which was in preview, will be removed as of August 1, 2024. Instead, Microsoft encourages you to use the Pod security admission controller functionality or the Azure policy service. -- 3). Management and Governance Azure Automation On August 31, 2024, change tracking and inventory with the Log Analytics agent will be removed. Instead you are encouraged to migrate to change tracking and inventory in Azure Monitoring Agent. The removal of the Update Management features, as well as the Log Analytics agent as of August 31, 2024. Azure Update Manager is the perfect replacement for Update Management, in fact I'm going to take a look at it because I might have some needed on one of my projects. Azure Monitor The removal of custom alerts from Container insights recommended alerts on May 31, 2024, instead of March 14, 2026. You are therefore encouraged to use the Prometheus rules instead. -- 4). Network VPN Gateway The withdrawal of the Standard and High Performance SKUs for the VPN gateway service on September 30, 2025. You will therefore need to consider using another SKU before this date to avoid any impact on your infrastructure. See you soon 😉Azure Container Apps - New Comic
- You are a Cloud lover? - But you prefer Azure? - Learning with fun? - And most of all, Containers are the best techno of the last couple of years? Maybe you'll like the last Azure Container Apps comic provided by Jules&Léa. 🥰 If you want to deep dive, do not hesitate to visit the official documentation on Microsoft: https://learn.microsoft.com/en-us/azure/container-apps/overview/?WT.mc_id=AZ-MVP-5005062 ++
