This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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.
All Operator/CRD MUST be installed explicitly
Operators and CRDs are implicitly installed via OLM and the explicit creation of subscriptions, which result in installplans etc. We don't look at it as the installer's job to set up operators and CRDs, but rather to set up subscriptions, and allow OLM to deal with the rest. That's just how OLM works. In the cases where we manually install CRDs/operators in our automation, it's only when there is no operator catalog carrying the necessary package available. Is there a specific thing that you have seen happening that has caused this feedback?
NO Operator/CRD MUST install automatically install another Operators/CRD
No Maximo operator will do this, however OLM does. e.g. a subscription to the ibm-mas operator package will result in two operators being installed in the namespace - IBM Maximo Application Suite Core Operator, and IBM Truststore Manager Operator. This is a fundamental feature of operator lifecycle manager (OLM).
All Operator/CRD MUST be pinned by to version i.e., no automatic mode
Every Maximo operator is versioned with semantic versioning, a new version will only ever be delivered via OLM, usually when the customer updates from one catalog to the next and this introduces an update on the currently subscribed channel, but also if the user changes the subscription channel.
NO wildcards in Kubernetes RBAC are allowed
Agreed, this is standard IBM policy. If anything is using a wildcard it's a bug
NO custom OpenShift would be allowed.
I don't understand this request, can you elaborate please?