Feature Request: zone redundancy information on replicas
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure
- Domain
- cloud
Research direction
Start by locating the existing replica and zone-redundancy information surfaces in Azure Container Apps; the issue names no files or tests. Define how each replica's availability zone should be exposed in a table, then verify that three replicas can display distribution across AZ 1, 2, and 3.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is
When zone redundancy has been enabled, there is no information on how the replicas are distributed across the zones.
Describe the solution you'd like.
A clear and concise description of what you want to happen, any scenarios it will unblock, etc.
There should be a table showing the replicas and the zones they have been deployed.
If there are 3 replicas, the zone column should show that the replicas are distributed across AZ 1, 2 and 3.
Describe alternatives you've considered.
A clear and concise description of any alternative solutions or features you've considered.
Additional context.
Add any other context or screenshots about the feature request here.
The information will assure that the deployment is able to meet the SLA of 99.95% and not concentrated within a zone.
- Dominant language
- Bicep
- Stars
- 445
- Forks
- 54
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/azure-container-apps
-
enhancement Needs: triage :mag:
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/azure-container-apps#1837 ·
-
Needs: triage :mag:
Difficulty 4/5 3-5 days Newbie friendliness 38/100
microsoft/azure-container-apps#1836 · 3 comments ·
-
August 2026 Updates OpenNeeds: triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
microsoft/azure-container-apps#1834 ·
-
Needs: triage :mag:
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/azure-container-apps#1833 · 1 comment ·
-
Needs: triage :mag:
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/azure-container-apps#1832 ·
All issues in microsoft/azure-container-apps
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
Feature needs-triage pulumi/registry
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
infrastructure launch: scale production
Difficulty 2/5 Half a day Newbie friendliness 72/100
Practitionist/familiarise_web#1772 ·