Currently Azure Container Registry stores container images in blobs. Unfortunately those blobs are only reachable over *.blob.core.windows.net - for obvious reasons this is not acceptable for egress traffic restrictions.
I am pleased that Microsoft Container Registry is no longer using the azure blob storage domain but the CDN (*.cdn.mscr.io) - what makes our lives much easier.
When can we expect similar thing to happen for public ACRs like aksrepos.azurecr.io? What is the current blocker? Lack of custom domain support with SSL in Azure Storage?
What is the plan for vnet-integrated ACRs? Are those going to support virtual network service endpoints for blobs as well? Is it going to integrate with Virtual Network Service Endpoint Policy?
This is a significant show-stopper for private AKS clusters...
Currently Azure Container Registry stores container images in blobs. Unfortunately those blobs are only reachable over *.blob.core.windows.net - for obvious reasons this is not acceptable for egress traffic restrictions.
I am pleased that Microsoft Container Registry is no longer using the azure blob storage domain but the CDN (
*.cdn.mscr.io) - what makes our lives much easier.When can we expect similar thing to happen for public ACRs like
aksrepos.azurecr.io? What is the current blocker? Lack of custom domain support with SSL in Azure Storage?What is the plan for vnet-integrated ACRs? Are those going to support virtual network service endpoints for blobs as well? Is it going to integrate with Virtual Network Service Endpoint Policy?
This is a significant show-stopper for private AKS clusters...