Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-1842

Expose routing and subnet details from IPAM CNI for vfio-pci SR-IOV devices to Pod

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • SDN
    • False
    • False
    • Undefined

      1. Proposed title of this feature request
      Expose routing and subnet details from IPAM CNI for vfio-pci SR-IOV devices to Pod

      2. What is the nature and description of the request?
      For a vfio-pci SR-IOV device (as opposed to kernel ones), the IP stack is implemented in the application itself, likely with the help of DPDK libraries. This implies that the application running inside the Pod must me aware of of what subnet prefix to use and what routes should be set up.
      The information on subnet prefix and default gw (and additional routes) is available in the IPAM CNI but it is currently not exposed to the application running inside the Pod.

      This RFE is about exposing all information which is available in the IPAM CNI to the application running in the Pod.
      Suggested interface for for this is the Downward API.

      There is no specific requirement that the information resides in */network-status annotation. Any annotation is fine as long as it can be exposed through Downward API.

      3. Why does the customer need this? (List the business requirements here)
      Without this ability, the network prefix and routing information need to be passed in through the helm chart with which the application is deployed. Which is suboptimal as the information is already present in the IPAM CNI.

              mcurry@redhat.com Marc Curry
              rhn-gps-djuran David Juran (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: