You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Ceph-CSI we run the e2e tests against a deployment inside minikube. There are currently two ways that Ceph-CSI is deployed, plain yaml files and Helm. When the ceph-csi-operator is available, it should be used to deploy Ceph-CSI in addition, and later on it should become the only way to deploy Ceph-CSI.
How will we know we have a good solution? (acceptance criteria)
Existing e2e test suites should work with ceph-csi-operator deployment
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.
Describe the feature you'd like to have
In Ceph-CSI we run the e2e tests against a deployment inside minikube. There are currently two ways that Ceph-CSI is deployed, plain yaml files and Helm. When the ceph-csi-operator is available, it should be used to deploy Ceph-CSI in addition, and later on it should become the only way to deploy Ceph-CSI.
How will we know we have a good solution? (acceptance criteria)
Existing e2e test suites should work with ceph-csi-operator deployment
Additional context
ceph-csi-operator: https://github.com/ceph/ceph-csi-operator
Tasks
The text was updated successfully, but these errors were encountered: