AB-449 Fix the release Dockerfile.jvm

[ThoSap]

The registry.redhat.io OCI image registry needs authentication, but registry.access.redhat.com does not.

#2 [internal] load metadata for registry.redhat.io/ubi9/openjdk-25-runtime:1.24
#2 ERROR: failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://registry.redhat.io/auth/realms/rhcc/protocol/redhat-docker-v2/auth?scope=repository%3Aubi9%2Fopenjdk-25-runtime%3Apull&service=docker-registry: 401 Unauthorized

[linear]

AB-449 PostgreSQL Operator

Based on the research and PoC done in the ticket and PR https://github.com/aboutbits/minio-operator/pull/1

We most likely will use CloudNativePG AB-396 for the DB Setup and this operator to manage the access, e.g. PostgreSQL roles and grants.

The scope of the operator is:

• Database/Schema management
• Role management
• Grant/Default Privilege management

[Copilot]

Pull request overview

This PR fixes a Docker build authentication issue by switching the base image registry from registry.redhat.io to registry.access.redhat.com. The change resolves a 401 Unauthorized error that occurs when pulling the OpenJDK runtime image without credentials.

Changes:

• Updated the base image registry URL in the JVM Dockerfile to use the publicly accessible registry

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.