Add workload test: KubeVirt/Containerized-Data-Importer
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 617
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 43
Description
# Describe the feature you'd like to have #
[Containerized-Data-Importer](https://github.com/kubevirt/containerized-data-importer) is a [KubeVirt](https://kubevirt.io) project that can work with CSI drivers. It is a straight forward workload that exercises many features of Ceph-CSI. In case a change breaks an external consumer like CDI, developers working on Ceph-CSI need to have a look at the cause and address it.
# What is the value to the end user? (why is it a priority?) #
Less chance on regressions for common consumers.
# How will we know we have a good solution? (acceptance criteria) #
There should be a CI job that runs the CDI smoke/happy-path tests regularly, possibly for each PR.
# Additional context #
See-also: kubevirt/containerized-data-importer#1289
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the CDI smoke/happy-path tests and the linked Containerized-Data-Importer issue #1289. Then trace how Ceph-CSI CI jobs are configured and determine how to run those tests regularly, with success defined as a CI job covering the CDI workload without regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- ci-cd, infrastructure, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100