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 Jan 13, 2026

Add support for local storage for MQ NativaHA in Edge scenarios

We are migrating our MQ on ACE Manufacturing pack on RHEL VMs located in factories which are edge sites with low resource footprint. MQ instances will be migrated using MQ Operator (SC-2 release) that supports NativeHA on Openshift 3 Node Cluster, each of the node coming from a physical server located on the factory. Today the creation of MQ Instance with NativeHA using MQ Operator (SC-2 release) requires specifying a storage class for dynamic provisioning but the issue is that these factories have no clustered storage or storage high availability, so it would be great if you could support local storage (Redhat LSO Operator) where we create the Persistent Volumes (PV) and specify these PV names in the MQ Instance CR yaml which would then create the PVCs from the PVs.

Today we workaround the limitation by creating the PVs and then PVCs in the name the MQ Instance CR expects.

Idea priority High