You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 9, 2022. It is now read-only.
Now that CRI supports a wildcard header for mirrors, we can have a problem implementing a pull through cache because of the ambiguity of the requested host (two different images with the same name on different backing registries). It also requires configuring the pull through cache to check all possible registries, since it does not know where the original image should be sourced.
If CRI were to set the X-Forwarded-Host header on the request, we could use that to solve both problems.
The text was updated successfully, but these errors were encountered:
This needs to be implemented in the containerd libraries and done in a consistent way. Closing this one as it is tracked already in containerd and OCI distribution spec.
Now that CRI supports a wildcard header for mirrors, we can have a problem implementing a pull through cache because of the ambiguity of the requested host (two different images with the same name on different backing registries). It also requires configuring the pull through cache to check all possible registries, since it does not know where the original image should be sourced.
If CRI were to set the X-Forwarded-Host header on the request, we could use that to solve both problems.
The text was updated successfully, but these errors were encountered: