Azure / Azure/AKS

[Feature] Application Gateway for Containers - Private/Internal Frontend IP Support

Open
#5,739 8 comments 21 reactions 2 assignees Claimed by @therealmitchconnors View on GitHub
app-gateway-for-containers feature-request fixing
Dominant language
TypeScript
Stars
2.1k
Forks
395
Avg merge
2d 22h
Merged PRs (30d)
13

Description

## Summary
Application Gateway for Containers (AGC) currently only supports public IP addresses for frontends. Please add support for a private/internal frontend IP, allowing the frontend to be bound to a private IP within a VNet subnet.

## Requested Feature
Support for:
- **Private-only frontend** — no public IP, internal traffic only
- **Dual frontend** — both a public and a private IP on the same AGC instance

Classic Application Gateway v2 already supports internal mode, so this would bring AGC to parity.

## References
- [AGC Frontends documentation](https://learn.microsoft.com/en-us/azure/application-gateway/for-containers/application-gateway-for-containers-components#application-gateway-for-containers-frontends)
- [Issue #5459](https://github.com/Azure/AKS/issues/5459) — private frontend acknowledged as unsupported

**Product:** Azure Application Gateway for Containers

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.