microsoft / microsoft/azure-container-apps
Feature Request: Ability to allow upstream TLS in addition to ingress TLS termination
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.
We want to enable HTTPs endpoints on our .net core apps hosted in container apps.
Currently if you do this, with a HTTPs ingress, the ingress cannot hand off the request instead returning a
upstream connect error or disconnect/reset before headers. retried and the latest reset reason: connection termination
Describe the solution you'd like.
The ability to allow self signed or in the case of say Let's Encrypt certificates, the ability to ignore name mismatches on the upstream endpoints.
Describe alternatives you've considered.
We've had to turn off TLS on the upstream application in the containers.
Additional context.
Add any other context or screenshots about the feature request here.
Works correctly if exposed using a TCP ingress.
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 concerns Azure Container Apps ingress and upstream TLS, but names no implementation files or tests. Start by reviewing the ingress TLS configuration and related roadmap issues; done means supporting upstream HTTPS with self-signed certificates or ignored hostname mismatches while retaining ingress TLS termination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100