-
Notifications
You must be signed in to change notification settings - Fork 558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run e2e with ceph-csi deployed via ceph-csi-operator #4856
Comments
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. |
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: