From b805e867bb73a9822c86c6710bb293bc6e76f7c4 Mon Sep 17 00:00:00 2001 From: Olivia Brown Date: Thu, 26 Sep 2024 10:04:41 -0400 Subject: [PATCH] Image registry bug batching 4.17 --- release_notes/ocp-4-17-release-notes.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/release_notes/ocp-4-17-release-notes.adoc b/release_notes/ocp-4-17-release-notes.adoc index feda484791..6ec33796d8 100644 --- a/release_notes/ocp-4-17-release-notes.adoc +++ b/release_notes/ocp-4-17-release-notes.adoc @@ -1551,6 +1551,12 @@ For existing storage accounts created before this update, shared access keys are + link:https://issues.redhat.com/browse/OCPBUGS-39428[(*OCPBUGS-39428*)] +* Previously, the image registry was unable to run due to a permissions error in the certificate directory. This issue has been resolved. (link:https://issues.redhat.com/browse/OCPBUGS-38885[*OCPBUGS-38885*]) + +* Previously, the internal image registry did not correctly authenticate users on clusters configured with external OIDC users because the internal image registry used the `user.openshift.io` and `oauth.openshift.io` APIs, which are not available on clusters configured with external OIDC users. Consequently, it was impossible for users to push or pull images to and from the internal image registry. With this update, the internal image registry uses the `SelfSubjectReview` API and the issue is resolved. (link:https://issues.redhat.com/browse/OCPBUGS-35335[*OCPBUGS-35335*]) + +* Previously, when enabling the `virtualHostedStyle` configuration with `regionEndpoint` set in the Image Registry Operator configuration, the image registry ignored the `virtualHostedStyle` configuration and failed to start. This update fixes the issue by using a new upstream distribution configuration, which uses force path style URLs, in favor of the downstream-only version, which is `virtualHostedStyle`. (link:https://issues.redhat.com/browse/OCPBUGS-32710[*OCPBUGS-32710*]) + [discrete] [id="ocp-4-17-installer-bug-fixes_{context}"] ==== Installer