Skip to Main Content
IBM Sustainability Software - Ideas Portal


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).


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 (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.

Status Future consideration
Created by Guest
Created on Aug 20, 2024

Installation procedure should also clearly define the RBAC policies/cluster role bindings /Certificate issuer policies

Similarly, due to segregation of duties, even namespace admins might not have access to all the APIs provided by the operators and to create instances/workspaces. RBAC policies might need to be defined in-order to gain access to the operator APIs and to create instances/services/workspace. So, installation procedure should also clearly define the RBAC policies/cluster role bindings /Certificate issuer policies with issuer details that might be needed in-order to gain access for the namespace admins/service accounts that calls/creates/updates the operator APIs/instances/workspaces/generate certificates etc.

Idea priority Medium
Needed By Quarter
  • Admin
    Lisa Stuckless
    Reply
    |
    Aug 21, 2024

    This is the same challenge of shifting our automation away from a simple "be cluster-admin" to a RBAC aware model; it's not simple, and it's not going to be quick. However, what we are seeing is that the customers that are interested in this wouldn't be using our ansible/CLI anyway and are looking either at the gitops solution we delivered this year, or like yourselves are looking to build their own. If there's a desire within Ford to use the MAS CLI to perform an install if it could be made RBAC aware then that would help add priority behind such work, but as with other customers, where we are seeing this kind of feedback we are also seeing a desire not to use the CLI in the first place, so at present there is questionable value in making changes in the CLI to support role-aware install/update/upgrade, which is why - so far - we are really only looking to address concerns in this area in terms of providing clear documentation about the roles involved.

    FWIW, if you are interested in the progress of this effort, the work in progress RBAC definition can be tracked here: https://github.com/ibm-mas/cli/tree/master/rbac/install