Skip to Main Content
Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Created by Guest
Created on Aug 27, 2026

Add ability to specify Storage "claimName" in App Connect dashboard "UI form" creation

We have our Cloud Pak for Integration (using IBM App Connect Operator 13.4.0) deployed to Azure Red Hat OpenShift (ARO); when we tried to create a new "App Connect dashboard" (in Platform Navigator) with the default settings, it failed due to being unable to properly create a Persistent Volume Claim (PVC), caused by restrictions in our Azure environment: For auditing/billing purposes, OpenShift is not allowed to dynamically request a Persistent Volume Claim (PVC), or at the very least the default naming convention does not match our Azure enforced naming convention.

We were able to get around this by going into YAML (rather than UI form) and adding a "claimName" specifying a (manually created) PVC which conformed to our naming conventions, but it would be nice if there was a way to specify the "claimName" in the UI form.

Idea priority Low