0773572e5d
* Remove a flaky part of the test that didn't add value. Signed-off-by: Alexander Wels <awels@redhat.com> Updated k8s image to latest. Refactored cluster up to allow for adding more providers easily. Signed-off-by: Alexander Wels <awels@redhat.com> * Updated k8s image to latest. Refactored cluster up to allow for adding more providers easily. Enable OKD 4.1 provider Signed-off-by: Alexander Wels <awels@redhat.com> |
||
|---|---|---|
| .github | ||
| api/openapi-spec | ||
| assets | ||
| automation | ||
| cluster-sync | ||
| cluster-up | ||
| cmd | ||
| doc | ||
| hack | ||
| manifests | ||
| pkg | ||
| tests | ||
| tools | ||
| vendor | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| doc.go | ||
| glide.lock | ||
| glide.yaml | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| stdci.yaml | ||
Containerized Data Importer
Containerized-Data-Importer (CDI) is a persistent storage management add-on for Kubernetes. It's primary goal is to provide a declarative way to build Virtual Machine Disks on PVCs for Kubevirt VMs
CDI works with standard core Kubernetes resources and is storage device agnostic, while its primary focus is to build disk images for Kubevirt, it's also useful outside of a Kubevirt context to use for initializing your Kubernetes Volumes with data.
Introduction
Kubernetes extension to populate PVCs with VM images
CDI provides the ability to populate PVCs with VM images upon creation. Multiple image formats and sources are supported:
Current supported Image formats
- .tar
- .gz
- .xz
- .img
- .iso
- .qcow2
Current supported image endpoints
- http
- S3
- local directory
DataVolumes
CDI also includes a CRD, that provides an object of type DataVolume. The DataVolume is an abstraction on top of the standard Kubernetes PVC and can be used to automate creation and population of a PVC for consumption in a Kubevirt VM.
Deploy it
Deploying the CDI controller is straightforward. In this document the default namespace is used, but in a production setup a protected namespace that is inaccessible to regular users should be used instead.
$ export VERSION=$(curl -s https://github.com/kubevirt/containerized-data-importer/releases/latest | grep -o "v[0-9]\.[0-9]*\.[0-9]*")
$ kubectl create -f https://github.com/kubevirt/containerized-data-importer/releases/download/$VERSION/cdi-operator.yaml
$ kubectl create -f https://github.com/kubevirt/containerized-data-importer/releases/download/$VERSION/cdi-operator-cr.yaml
Use it
Create a DataVolume and populate it with data from an http source
$ kubectl create -f https://raw.githubusercontent.com/kubevirt/containerized-data-importer/$VERSION/manifests/example/import-kubevirt-datavolume.yaml
There are quite a few examples in the example manifests, check them out as a reference to create DataVolumes from additional sources like registries, S3 and your local system.
Hack it
CDI includes a self contained development and test environment. We use Docker to build, and we provide a simple way to get a test cluster up and running on your laptop. The development tools include a version of kubectl that you can use to communicate with the cluster. A wrapper script to communicate with the cluster can be invoked using ./cluster-up/kubectl.sh.
$ mkdir $GOPATH/src/kubevirt.io && cd $GOPATH/src/kubevirt.io
$ git clone https://github.com/kubevirt/containerized-data-importer && cd containerized-data-importer
$ make cluster-up
$ make cluster-sync
$ ./cluster-up/kubectl.sh .....
Connect with us
We'd love to hear from you, reach out on Github via Issues or Pull Requests!
Hit us up on Slack, under the Kubernetes Virtualization channel
Shoot us an email at: kubevirt-dev@googlegroups.com