Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-20702

KubeVirt network binding plugin interface

XMLWordPrintable

    • net-binding-plugins
    • Hide
      • (must-have) Custom network binding can be used without a need to re-build KubeVirt
      • (must-have) Upstream documentation describing the interface and how to use it
      • (must-have) The interface can be used with CNV deployment
      • (must-have) This feature must work with the hook sidecar gate closed - users must not be able to request an arbitrary hook sidecar
      • (must-have) KCS documenting how to utilize this, where to look for reference implementation, API, explaining how stable the API is, and what is Red Hat's level of support to our partners
      • (should-have) One reference plugin implementation
      • No QE
      • No UXD
      • No D/S docs, the documentation team will review KCS article written by dev
      Show
      (must-have) Custom network binding can be used without a need to re-build KubeVirt (must-have) Upstream documentation describing the interface and how to use it (must-have) The interface can be used with CNV deployment (must-have) This feature must work with the hook sidecar gate closed - users must not be able to request an arbitrary hook sidecar (must-have) KCS documenting how to utilize this, where to look for reference implementation, API, explaining how stable the API is, and what is Red Hat's level of support to our partners (should-have) One reference plugin implementation No QE No UXD No D/S docs, the documentation team will review KCS article written by dev
    • Green
    • To Do
    • CNV-30157 - Simplified pod network with plugins
    • CNV-30157Simplified pod network with plugins
    • 0% To Do, 0% In Progress, 100% Done
    • dev-ready, doc-ready, po-ready, qe-ready, ux-ready
    • Hide

      2024-02-14: On track, everything required for the release was merged...

      Show
      2024-02-14: On track, everything required for the release was merged...

      Goal

      Allow contributors to supply their custom network bindings without a need to maintain them under kubevirt/kubevirt.

      User Stories

      • As a KubeVirt contributor,
        I need a custom network binding,
        to support my specific requirements.
      • As a KubeVirt maintainer,
        I cannot easily accept new network bindings,
        as they extend the test matrix considerably
        and I don't have capacity or domain knowledge to support them in the long run.
      • As a Red Hat partner,
        I want to ship my custom network binding alongside OpenShift Virtualization.

      Non-Requirements

      • It is not required to convert existing bindings into plugins.
      • This feature is focused on upstream only, not need for QE or product documentation changes. It should be however shipped with downstream and possible to use on downstream deployments (so partners can start playing with it).

      Notes

      Done Checklist

      Who What Reference
      DEV Upstream roadmap issue (or individual upstream PRs) N/A
      DEV Upstream documentation merged https://kubevirt.io/user-guide/virtual_machines/network_binding_plugins/
      DEV gap doc updated N/A
      DEV Upgrade consideration Upgrade path from in-tree bindings was considered and documented
      DEV CEE/PX summary presentation N/A
      QE Test plans in Polarion N/A
      QE Automated tests merged N/A
      DOC Downstream documentation merged N/A

            phoracek@redhat.com Petr Horacek
            phoracek@redhat.com Petr Horacek
            Petr Horacek Petr Horacek
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: