Skip to Main Content

This is an IBM Automation portal for Integration products. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

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.

Status Not under consideration
Workspace API Connect
Created by Guest
Created on Jun 17, 2022

API Connect air gap installation with the internal Red Hat OpenShift registry

The customer is about to install API Connect v10 into an OCP (ROSA) environment. This customer is installing by AirGap for their security policy.

However, the OCP (ROSA) repository is not available for constraints.

  • Supports Docker Manifest V2, Schema 2.

    • The internal Red Hat OpenShift registry is not compliant with Docker Manifest V2, Schema 2, so it is not suitable for use as a private registry for restricted environments.

  • Allows path separators in the image name.

This customer is looking for a consistent installation procedure between IBM and RedHat.
The customer needs API Connect installation procedure with standard repositories provided by OCP.

Idea priority Medium
  • Admin
    Dan Temkin
    Aug 15, 2022

    OCP registry is not supported as a mirror registry as it doesn't support multiple path in image path. Our image path is as following {registry}/cp/apic/{image} and APIC is following standards across IBM Container software and Cloud Paks. The RedHat OCP built-in local repository would need to be enhanced to support path separators.

    Customers can also choose to External registries such as Quay (OSS or Red Hat distribution), JFrog, Nexus, Harbor have been used as they support our requirements.

    At this time we are not evaluating change to our repository requirements.