Skip to content

Commit c9b1a35

Browse files
integrating with AKS
1 parent 19f188a commit c9b1a35

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/container-registry/container-registry-private-link.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -465,6 +465,10 @@ If you created all the Azure resources in the same resource group and no longer
465465
az group delete --name $RESOURCE_GROUP
466466
```
467467

468+
## Integrating with AKS
469+
470+
Once the private link configuration to the ACR is successfully complete, the registry handles the pull requests through the data endpoints. You have to update the routing configuration for the client proxy and client firewall with the data endpoints to handle the pull requests successfully. A client proxy will provide central traffic control to the [outbound requests][outbound-connection]. To handle local traffic a client proxy is not required, you can add into `noProxy` section to bypass the proxy. Requests to token server over private endpoint connection doesn't require the data endpoint configuration.
471+
468472
## Next steps
469473

470474
* To learn more about Private Link, see the [Azure Private Link](../private-link/private-link-overview.md) documentation.
@@ -510,3 +514,4 @@ az group delete --name $RESOURCE_GROUP
510514
[quickstart-portal]: container-registry-get-started-portal.md
511515
[quickstart-cli]: container-registry-get-started-azure-cli.md
512516
[azure-portal]: https://portal.azure.com
517+
[outbound-connection]: /azure/firewall/rule-processing#outbound-connectivity

0 commit comments

Comments
 (0)