Using Cache for Docker Hardened Images (dhi.io) is not working anymore.

[JuergetSTatVGOA]

Describe the bug
We configured caching rules for dhi.io on several ACR's 2 months ago.
Credentials are stored in Azure Keyvaults.
Up from today, this integration is no longer working.
All our credentials got unhealthy and we get the message:

Sequence contains no elements

pulling any image like follows
docker pull xxx.azurecr.io/dhi/beat-exporter:0-debian-dev
leads to error message:
Error response from daemon: error from registry: authentication required, visit https://aka.ms/acr/authorization for more information. CorrelationId: 9788c9dc-17f9-4718-b7c3-10da8669d899

To Reproduce
Steps to reproduce the behavior:

1. Configure Cache Rule for ACR pointing to RepositoryPath dhi.io/*
2. Configure credentials for docker dhi, with key vault as source
3. Allow "KeyVault secret User" access for the used Identity Principal Id on the key vault

Expected behavior
ACR should login to dhi.io, pull image and provide it for docker pull

Any relevant environment information
Probably, the login server changed.
For pulling directly from dhi.io one hast to do "docker login dhi.io" now, instead of "docker.io"
There is no dhi.io option available in Cache Rule though

[luisdlp]

Hello. We identified a regression in a recent deployment that is causing these issues with some images from DHI. We will be rolling back this deployment today for registries that are using caching rules with DHI.

[luisdlp]

We've disabled the feature that caused the regression for registries targeting DHI.
@JuergetSTatVGOA can you please confirm to us if you are unblocked?

[original-codematrix]

@luisdlp it has been confirmed on our side that the pulling now works again.

[JuergetSTatVGOA]

We could also confirm. Thanks !

[luisdlp]

This issue has been resolved.