Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-190

SPIKE: Define process for removing users & cleaning up resources

XMLWordPrintable

    • 2
    • False
    • False
    • Hide

      1. Design document for processes/issues related to removing users as defined in description.

      Show
      1. Design document for processes/issues related to removing users as defined in description.
    • No
    • No
    • Undefined
    • No
    • Pending
    • MODH Sprint 17

      As a RHODS admin, I need to be able to remove users so they can no longer access the service. For example, a user may change roles or leave the company.

      This story is to investigate and document processes related to removing users:

      • For removed users, the user-specific PVs and other resources should remain. The assumption is that at a minimum, admins should be able to access these resources & manually take actions to preserve or delete resources.
      • How can admins view contents of PVs
      • Can they back up & remove resources (PVs, config maps, keys) tied to the removed user?
      • Could they grant access to user-specific resources to another user?
      • Future - consider some type of automated cleanup & removal of user-specific resources. 

              aasthana@redhat.com Anish Asthana
              jdemoss@redhat.com Jeff DeMoss
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: