Azure Container App notes

00-Environment-network-and-zone-redunancy.md

Azure Container App notes | Enviroment networking and redunancy

Consume only type

Consumption only environments should be ignored:

• Legacy
• Portal does not even support creation of that kind of environments

Zone-redunancy

The documentation and implementation for zone-redunancy requirements is conflicting.

Documentation 1 / portal

• https://learn.microsoft.com/en-us/azure/reliability/reliability-azure-container-apps?tabs=azure-cli
• Zone redunancy can be enabled for both Internal and External Virtual IP
  • You can select Internal or External for the Virtual IP
• Portal allows both

Azure CLI

• Azure CLI requires user to pass --infrastructure-subnet-resource-id with --zone-redundant

Azure Powershell module

• Cmdlet are just facade for API

PSRule

PSRule requires:

• Set the properties.zoneRedundant property to true.
• Set the properties.vnetConfiguration.infrastructureSubnetId property to reference a valid subnet.

Landing zone accelerator

• https://github.com/Azure/aca-landing-zone-accelerator
• Does not contain proper documentation for other use cases than internal VNet usage

infrastructureSubnetId requirement

AZ CLI

• AZ CLI requires --infrastructure-subnet-resource-id if --internal-only enabled
• --infrastructure-subnet-resource-id can be passed if --internal-only not present
  • Does it make any sense?

Portal

• Portal required infrastructure subnet ID even for external load balancer configurations
  • load balancer does not use subnet being used

Manual experimentation

• Try to solve this?

Managed inftrastructure without VNet

Az Powershell

• Enabled when not passing --infrastructure-subnet-resource-id or --internal-only

Portal

• vnetConfiguration = null

Remaining questions

• Does managed environent support zone redunancy?

AVM module

• WTF
  • Mandatoru networking params for WAF: https://learn.microsoft.com/en-us/azure/container-apps/vnet-custom?tabs=bash&pivots=azure-cli#networking-parameters
    • There are three optional networking parameters you can choose to define when calling containerapp env create. Use these options when you have a peered VNET with separate address ranges. Explicitly configuring these ranges ensures the addresses used by the Container Apps environment don't conflict with other ranges in the network infrastructure.

02-Environment-logging.md

Azure Container App notes | Enviroment logging

REST API and Bicep documentation states following

Cluster configuration which enables the log daemon to export app logs to a destination. Currently only "log-analytics" is supported

Source: https://learn.microsoft.com/en-us/azure/templates/microsoft.app/2024-03-01/managedenvironments?pivots=deployment-language-bicep#managedenvironmentproperties

AVM

AVM has a note about RP bug:

Existing Log Analytics Workspace resource ID. Note: This value is not required as per the resource type. However, not providing it currently causes an issue that is tracked here.

Linked ticket: Azure/bicep-types-az#1407

TODO:

Test this