Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps 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 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.