Feature Request: Azure Front Door ingress for private environment support/example

[madhancock]

Is your feature request related to a problem? Please describe.
I've put this up on the Front Door community also: https://feedback.azure.com/d365community/idea/01498c46-b232-ed11-a81b-000d3ae3db6e

Either documentation on how to correctly use Azure Front Door as a gateway to a private container environment. This seems to be possible using AKS using a private link to the internal load balancer and, as you'll see in the link - I was able to get it working for a short time. But there was also some strange behaviour that I was not able to confirm if it was caused by Front Door or ACA.

Describe the solution you'd like.
Documentation or confirmation it's not currently possible.

Describe alternatives you've considered.
I've tried following examples with AKS, however the origin configuration needed to prevent unexpected behaviours and to ensure ingress functions as expected isn't 100% clear:

Additional context.
Being able to do this would allow for use of WAF features and traffic management/auditing, ensuring those features cannot be bypassed by going direct to the ACA URLs (which would be possible if a public ACA was used as an origin).

[kendallroden]

Thanks for your request. I will dig into this and update when possible

[kendallroden]

@swgriffith

[Ricky-G]

Keen to know if its on the road map, private endpoint support for ACA

[madhancock]

@kendallroden Any update you can share on this?

[kendallroden]

@madhancock we are working on documentation, but is there any way you can elaborate on the "strange behaviors" you were observing?