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 (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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.