-
Notifications
You must be signed in to change notification settings - Fork 547
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
Enable more tests for the k8s-e2e-external-storage job #2015
Comments
Updates: ceph#2015 Signed-off-by: Niels de Vos <[email protected]>
Edit: This comment has been moved into its own issue: #2017 (comment) |
Updates: ceph#2015 Signed-off-by: Niels de Vos <[email protected]>
Updates: #2015 Signed-off-by: Niels de Vos <[email protected]>
Updates: ceph#2015 Signed-off-by: Niels de Vos <[email protected]>
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 closed due to inactivity. Please re-open if this still requires investigation. |
Currently busy with other features, not working on this atm. |
Removing this from the 3.5 milestone tracker. |
Thanks, @Rakshith-R for assigning, will work on it. |
@yati1998 shall we remove this from the release 3.6 tracker ? |
yes. |
@yati1998 is this something we are making progress ? if yes, please feel free to link , I was looking into this partially and PRs like #3156 were a start, however I am doubtful that the pending tests will be able to bring up soon on at 3.7 which is planned at end of this month. Unless there is something which you are already working on, I would like to propose to move this out of 3.7. |
Yes, I am working on this by side, but facing issues to run tests locally. Will try to get something for 3.7, but still not sure. I will link once I have something. Hope that's fine. |
Sure, please adjust the tracker accordingly, we have a week more atleast. |
The
ci/centos/k8s-e2e-external-storage
runs the Kubernetes end-to-end external storage tests, based on the differentdriver-*.yaml
files. These driver files describe the capabilities of the provisioner.Currently many features are not enabled in the drivers-test configuration. We ate aiming to have have all features that the provisioners support tested by the Kubernetes external storage tests. Each option that gets enabled should ideally be submitted by its own PR, referencing this Issue, use:
The text was updated successfully, but these errors were encountered: