-
Notifications
You must be signed in to change notification settings - Fork 537
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
Add e2e tests #32
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/assign |
Running upstream e2e tests works, but we should skip Disruptive for now.
|
SGTM. Let's create a different issue to track this if you are going to focus on e2e test case for this issue.
This is the least we can do, but this approach also provides the least value. Can we do better? |
'should concurrently access the single volume from pods on different node' will cover RWX mode from multiple pods. Will look into other ways to verify traffic is actually encrypted. May be tricky, might need to start a privileged pod on the node to for example check if there is an stunnel process for the mount |
/close |
@leakingtapan: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
STOR-1017: Rebase to v1.4.8
Is your feature request related to a problem? Please describe.
We should add e2e test for supported features:
The text was updated successfully, but these errors were encountered: