• Product / Portfolio Work
    • None
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • S
    • None

      Feature Overview (aka. Goal Summary)  

      Have Zonal volume support for the OpenShift Operator

      The EFS operator driver image does not have botocore and cannot fall back to DescribeMountTargets when file system DNS resolution fail. 

      This appears to require python3-botocore package in order to fall back to DescribeMountTargets when file system DNS resolution fail. This package does not exist in RHEL so we need to find the best way to pull it in.

      Should be testonly besides this.

      Goals (aka. expected user outcomes)

       

      Allow the EFS CSI driver to DescribeMountTargets when file system DNS resolution fail. 

      Requirements (aka. Acceptance Criteria):

      Find a way to include botocore in our image or any alternative

      Make sure that when DNS fail it falls back to DescribeMountTargets

       

      Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

      Deployment considerations List applicable specific needs (N/A = not applicable)
      Self-managed, managed, or both both
      Classic (standalone cluster) y
      Hosted control planes y
      Multi node, Compact (three node), or Single node (SNO), or all all
      Connected / Restricted Network all
      Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) AWS only
      Operator compatibility EFS
      Backport needed (list applicable versions) no
      UI need (e.g. OpenShift Console, dynamic plugin, OCM) no
      Other (please specify) AWS ONLY

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

      <your text here>

      Questions to Answer (Optional):

      How to include botocore in our images

      Out of Scope

      N/A

      Background

      CSI driver supports falling back to DescribeMountTargets but we're missing the python3-botocore package.

      Customer Considerations

      Should be transparent to customer in terms of configuration and they would automatically benefit from zonal volumes

      Documentation Considerations

       

      • we need a RN that One Zone volumes are supported
      • we need to remove / replace note that One Zone volumes are not supported
        • we need a new note that dynamic provisioning of One Zone volumes is supported only in single-zone clusters. All nodes in the cluster must be in the same availability zone as the EFS volume that's used for the dynamic provisioning.
        • we do support manually provisioned One Zone volumes in regional clusters, assuming the PVs have correct `spec.nodeAffinity` that tells in what zone the volume is. Ask rhn-engineering-jsafrane or  rhn-support-pewang for an example if you need one.

      Interoperability Considerations

      AWS / ROSA

              rh-gs-gcharot Gregory Charot
              rh-gs-gcharot Gregory Charot
              None
              None
              Jan Safranek Jan Safranek
              Jan Safranek Jan Safranek
              Penghao Wang Penghao Wang
              Lisa Pettyjohn Lisa Pettyjohn
              Eric Rich Eric Rich
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: