Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

Status Under review
Created by Guest
Created on Jan 12, 2024

Install CP4D using private registry in OCP with unqualified-search-registries configuration

If you are planning the installation of CP4D, but the customer has OCP configured with unqualified-search-registries (called also "image short names" and configured in image registry via containerRuntimeSearchRegistries). So, during installation, you should have to leave empty the PRIVATE_REGISTRY_LOCATION environment variable  as all images will be referred without registry host; for example, normally you pull an image form custom private registry as

but in the customer environment we have to indicate the image as


Actually it's not possible to leave empty the PRIVATE_REGISTRY_LOCATION environment variable during installation.

Furthermore, through the creation of the ImageContentSourcePolicy, the images are still referenced by referring to the source and, forcing the client to add them to the allowed sources in image.config.

The idea is to have the possibility to proceed with an installation where the images are not qualified, respecting the configurations imposed by policies in the client's OCP clusters.

Needed By Quarter