Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-9480

Pre-create che-admin and che-admin-read-only ClusterRoles

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Release Notes
    • Hide
      = `che-admin` and `che-admin-read-only` ClusterRoles are now pre-created

      To simplify administration and GitOps integration, Dev Spaces now pre-creates two `ClusterRoles` during installation. You can now reference these roles directly in `ClusterRoleBindings` without needing to define them manually.

      The new roles are:

      * `che-admin`: Provides full administrative access to Dev Spaces resources.

      * `che-admin-read-only`: Provides read-only access to Dev Spaces resources.

      For more information, see the documentation about link:https://placeholder-for-admin-guide-link[Managing user permissions].
      Show
      = `che-admin` and `che-admin-read-only` ClusterRoles are now pre-created To simplify administration and GitOps integration, Dev Spaces now pre-creates two `ClusterRoles` during installation. You can now reference these roles directly in `ClusterRoleBindings` without needing to define them manually. The new roles are: * `che-admin`: Provides full administrative access to Dev Spaces resources. * `che-admin-read-only`: Provides read-only access to Dev Spaces resources. For more information, see the documentation about link: https://placeholder-for-admin-guide-link [Managing user permissions].
    • Enhancement
    • Proposed
    • Red Hat OpenShift Dev Spaces

      < High-Level description of the feature ie: Executive Summary >

      Goals

      The minimal set of permissions required to install the project is documented as part of https://eclipse.dev/che/docs/stable/administration-guide/permissions-to-install-che/

      However, it would be nice to pre-create che-admin and che-admin-read-only ClusterRoles that would be easy to reference from Argo / GitOps

      Requirements

      Requirements Notes IS MVP
           

        • (Optional) Use Cases

      < What are we making, for who, and why/what problem are we solving?>

      Out of scope

      <Defines what is not included in this story>

      Dependencies

      < Link or at least explain any known dependencies. >

      Background, and strategic fit

      < What does the person writing code, testing, documenting need to know? >

      Assumptions

      < Are there assumptions being made regarding prerequisites and dependencies?>

      < Are there assumptions about hardware, software or people resources?>

      Customer Considerations

      < Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

      Documentation Considerations

      < What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >

      What does success look like?

      < Does this feature have doc impact? Possible values are: New Content, Updates to existing content, Release Note, or No Doc Impact?>

      QE Contact

      < Are there assumptions being made regarding prerequisites and dependencies?>

      < Are there assumptions about hardware, software or people resources?>

      Impact

      < If the feature is ordered with other work, state the impact of this feature on the other work>

      Related Architecture/Technical Documents

      <links>

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

              abazko Anatolii Bazko
              mbenitez@redhat.com Martha Benitez
              Gaurav Trivedi Gaurav Trivedi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: