Uploaded image for project: 'OpenShift Storage'
  1. OpenShift Storage
  2. STOR-1379

Techdebt: Automatic resource deletion for GCP Filestore

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Techdebt: Automatic resource deletion for GCP Filestore
    • 2
    • True
    • Installation of GCP clusters is currently broken
    • False
    • Yellow
    • To Do
    • OCPSTRAT-768 - Apply user defined tags to all resources created by OpenShift (GCP) GA
    • OCPSTRAT-768Apply user defined tags to all resources created by OpenShift (GCP) GA
    • 0% To Do, 25% In Progress, 75% Done
    • XS

      Epic Goal*

      GCP Filestore instances are not automatically deleted when the cluster is destroyed.

       
      Why is this important? (mandatory)

      The need to delete GCP Filestore instances is documented. This is however inconsistent with other Storage resources (GCP PD), which get removed automatically and also may lead to resource leaks

      Scenarios (mandatory) 

      Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

      1. User installs a GCP cluster
      2. User creates a new Filestore instance as per the documentation: https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/persistent-storage-csi-google-cloud-file.html
      3. User does not delete the Filestore instance but destroys the cluster
      4. The Filestore is not removed and may impose additional cloud costs

       
      Dependencies (internal and external) (mandatory)

      This requires changes in the GCP Filestore Operator, GCP Filestore Driver and the OpenShift Installer

      Contributing Teams(and contacts) (mandatory) 

      Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

      • Development - 
      • Documentation -
      • QE - 
      • PX - 
      • Others -

      Acceptance Criteria (optional)

      Provide some (testable) examples of how we will know if we have achieved the epic goal.  

      Drawbacks or Risk (optional)

      Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

      Done - Checklist (mandatory)

      The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

      • CI Testing -  Basic e2e automationTests are merged and completing successfully
      • Documentation - Content development is complete.
      • QE - Test scenarios are written and executed successfully.
      • Technical Enablement - Slides are complete (if requested by PLM)
      • Engineering Stories Merged
      • All associated work items with the Epic are closed
      • Epic status should be “Release Pending” 

            rhn-support-tsmetana Tomas Smetana
            rhn-support-tsmetana Tomas Smetana
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:

                Estimated:
                Original Estimate - 2 weeks
                2w
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 weeks
                2w