Is your feature request related to a problem? Please describe.
I'm deploying an internal-only Container Apps Environment with Bicep (infra as code). During deployment, an IP address seems to be randomly picked from the subnet that I provided as the properties.vnetConfiguration.infrastructureSubnetId.
Although this is a static IP address for the lifetime of the Container Apps Environment, a new deployment usually gives me a new static IP address. It is therefore not possible to redo a deployment idempotently, and automatically restore connectivity from other apps to the Container Apps Environment.
Describe the solution you'd like.
Possible solutions that could make the IP address static over (re)deployments:
An option to provide the properties.staticIP, when properties.vnetConfiguration.internal: true.
Keep doing automatic address assignments, but make sure it is always chosen from a specific positition in the subnet. For example, always pick the before-last IP address from the subnet.
Is your feature request related to a problem? Please describe.
I'm deploying an internal-only Container Apps Environment with Bicep (infra as code). During deployment, an IP address seems to be randomly picked from the subnet that I provided as the
properties.vnetConfiguration.infrastructureSubnetId.Although this is a static IP address for the lifetime of the Container Apps Environment, a new deployment usually gives me a new static IP address. It is therefore not possible to redo a deployment idempotently, and automatically restore connectivity from other apps to the Container Apps Environment.
Describe the solution you'd like.
Possible solutions that could make the IP address static over (re)deployments:
properties.staticIP, whenproperties.vnetConfiguration.internal: true.