Closed sutirtha-bagchi-21 closed 1 month ago
@sutirtha-bagchi-21 Thanks for your feedback! We will investigate and update as appropriate.
@sutirtha-bagchi-21 Can you please check and add your comments on this request as applicable.
Thank you for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner, and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
[Enter feedback here]
Hi Team, my customer is following this document and asking if we need the second route (Firewll Public Ip > next Hop Internet) on the route table as this is not a common practice for any other azure service egress setup. So customer is why would we need that and if they do not add it, will it break anything. Also our recommendation is to update this docunments to add a brief explanation behind the need of adding the second route to the route table.
Refer to the section https://learn.microsoft.com/en-us/azure/aks/limit-egress-traffic?tabs=aks-with-system-assigned-identities#create-a-route-with-a-hop-to-azure-firewall and bullet #20635
az network route-table route create -g $RG --name $FWROUTE_NAME_INTERNET --route-table-name $FWROUTE_TABLE_NAME --address-prefix $FWPUBLIC_IP/32 --next-hop-type Internet.
Thanks, Sutirtha Bagchi, Microsoft, Infra CSA
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.