This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
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 |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
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.
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.