Skip to content

Latest commit

 

History

History
20 lines (13 loc) · 2.29 KB

supported_operations.md

File metadata and controls

20 lines (13 loc) · 2.29 KB
Raw

Containerized Data Importer supported operations

The Containerized Data Importer (CDI) supports importing data/disk images from a variety of sources, and it can be hard to understand which combination of operations is supported and if that operation requires scratch space. This document explains the combinations that are supported and which ones require scratch space. All Kubevirt content-type operations will support both file system Data Volumes (DV) as well as block volume DVs.

Supported matrix

The first column represents the available content-types, Kubevirt and Archive. Kubevirt is broken down into QCOW2 vs RAW. QCOW2 needs to be converted before being written to the DV (and in a lot of cases requires scratch space for this conversion), where RAW doesn't need conversion and can be written directly to the DV.

http https http basic auth Registry S3 Bucket Upload
KubeVirt(QCOW2)
  • QCOW2
  • GZ*
  • XZ*
  • QCOW2**
  • GZ*
  • XZ*
  • QCOW2
  • GZ*
  • XZ*
  • QCOW2*
  • GZ
  • XZ
  • QCOW2*
  • GZ*
  • XZ*
  • QCOW2*
  • GZ*
  • XZ*
KubeVirt (RAW)
  • RAW
  • GZ
  • XZ
  • RAW
  • GZ
  • XZ
  • RAW
  • GZ
  • XZ
  • RAW*
  • GZ
  • XZ
  • RAW
  • GZ
  • XZ
  • RAW*
  • GZ*
  • XZ*
Archive+
  • TAR
  • TAR
  • TAR
  • TAR
  • TAR
  • TAR

* Requires scratch space

** Requires scratch space if a custom CA is required.

+ Archive does not support block mode DVs

From a technical perspective uploading a RAW kubevirt image doesn't require scratch space, however we can't tell ahead of time if the data coming in is raw or not, so we have to attach scratch to the upload server pod even if we don't use it.