Skip to Main Content
Cloud Management and AIOps

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:

Post your ideas

Start by posting 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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):

  • Cloud Pak for Multicloud Management

  • Cloud Pak for Network Automation - incl Orchestration and Performance Management

  • Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio

  • Edge Application Manager

  • IBM Observability with Instana

  • ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8

  • Workload Automation - incl Workload Scheduler

  • Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)

  • Tivoli Application Dependency Discovery Manager - TADDM

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

Status Planned for future release
Created by Guest
Created on Mar 6, 2020

Improvement of the Deployment of CA signed certificate for cp4mcm product

Openshit Version : 4.2

Cloudpak-MCM version : 1.2.0 Enterprise

Hosting Cloud : AWS

Background: During CP4MCM installation , installer expects the certificate (BYOC) to be located inside cfc-component directory which works perfectly fine.

Feature enhance of CP4MCM installer : Can we leverage the installer to handle this automatically ?

something like this:

During installation if we can pass some parameter to installer which should determine if it should get the certificate from the cluster secrets and update the certificate in the cfc-component directory before triggering the installation.

oc get secrets -n openshift-ingress router-certs-letsencrypt --export -o yaml

Note: cp4mcm component uses self signed certificate until you explicitly keep the certificates in the cfc-component directory.

Idea priority Medium
  • Guest
    Mar 10, 2020

    We are working on a highly visible program at GBS (Red Hat OpenShift Everywhere Experiential Campaign) and Cloud Paks are an integral part of it. Capabilities like the one requested here the critical foundational services for us to do this at scale (e.g. 400 instance provisioning in one quarter). As the underlying OCP cluster is already having a CA signed certificate, we expect the CP4MCM installer to just pick it instead of expecting the user to supply the same thing again manually.

  • Admin
    Matt Rodkey
    Mar 9, 2020

    We definitely are interested in improving our deployment of certs. In our next release we are refactoring our installer to be operator based. Once we complete our refactoring work we can come back add investigate a solution.