microsoft / microsoft/azure-container-apps
Feature Request: Preserve Client IP address for TCP ingress using Proxy Protocol
Nobody has claimed this yet.
- Dominant language
- Bicep
- Stars
- 445
- Forks
- 54
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
For TCP ingress, provide a way to access the client IP Address.
Describe the solution you'd like.
I need to know the client IP address for whitelisting, blacklisting, and logging client IP Addresses. Since Azure Container apps uses the Envoy proxy, preserving the client IP Address should be possible using the proxy protocol feature.
Describe alternatives you've considered.
The only alternative currently is not to use container apps and host the service inside of a VM with a public IP Address.
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.
Research direction
The issue names Azure Container Apps, TCP ingress, and Envoy's Proxy Protocol support but does not identify files, tests, or an entry point. Start by determining where TCP ingress behavior is defined and whether Proxy Protocol is supported; done means a documented and usable way to preserve and access the client IP for whitelisting, blacklisting, and logging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100