-
Notifications
You must be signed in to change notification settings - Fork 808
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
WIP: Add external Kubernetes tests #473
Conversation
Tests imported from Kubernetes will be used for more than migration tests.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsafrane The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Pull Request Test Coverage Report for Build 1052
💛 - Coveralls |
I tested it in my AWS account - it installs 1.15 cluster, runs AWS EBS driver there and runs 1.16 tests against the driver. The test don't pass - as it runs 1.16 tests, expecting 1.16 cluster. I haven't been able to install Kubernetes 1.16 with Looking at https://github.com/aws/aws-k8s-tester, it hardcodes kops 1.14.alpha. Is there any plan to move to 1.17? Whole k8s-e2e-tester is quite cryptic, it does not log anything and I can't even get Kubernetes logs from it. |
0c3ea19
to
3e5da35
Compare
tester/external-config.yaml
Outdated
@@ -0,0 +1,75 @@ | |||
cluster: | |||
kops: | |||
stateFile: s3://jsafrane-k8s-kops-csi-e2e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix the s3 path
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
echo "Deploying driver" | ||
# install helm | ||
OS_ARCH=$(go env GOOS)-amd64 | ||
helm_name=helm-v2.14.1-$OS_ARCH.tar.gz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use helm3?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer all config.yamls to be the same and the rest uses 2.14.
Max: 16Ti | ||
SupportedFsType: | ||
xfs: {} | ||
ext4: {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add ext2 and ext3 since they are supported too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure it brings any real value. It only doubles number of tests. It's served by ext4 kernel module anyway.
|
||
# Update dependencies | ||
```sh | ||
go mod edit -require=k8s.io/kubernetes@v1.15.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which k/k version supports external tests? Update this accordingly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version of installed kubernetes and tests should be the same. Running newer version of the tests against older kubernetes will test features that are not enabled by default or run regression tests for bugs that were not fixed yet. That's why 1.15.
As I wrote above, we need 1.17 cluster or even 1.18 to run some real tests. But I don't know how to install it with k8s-e2e-tester.
To make sure migration test also works |
/test pull-aws-ebs-csi-driver-migration-test-latest |
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. |
@jsafrane: PR needs rebase. 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. |
Stale issues rot after 30d 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 |
/remove-lifecycle rotten |
/remove-lifecycle stale |
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. |
Stale issues rot after 30d 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. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closed this PR. 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. |
@ayberk: Reopened this PR. 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. |
@jsafrane: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
Yes we do. The e2e-migration test setup is not good enough, it's failing since inline migration fix is not in yet, so can't be presubmit, and anyway we should run the same tests with migration on AND off. I can rebase and pick this up from jsafrane, I revamped the run-e2e-test script recently and it doesn't rely on the tester binary so it should be easier to keep up with k/k test/e2e |
Hi @wongma7, are you still actively working on this issue? |
/close thanks all, we picked this up in #726 |
Fixes #470
What is this PR about? / Why do we need it?
Kubernetes offers so called external tests, where it can run e2e tests against an installed CSI drivers.
See https://github.com/kubernetes/kubernetes/tree/master/test/e2e/storage/external
As consequence, I renamed
tests/e2e-migration
totests/e2e-kubernetes
, because both external & migration tests are there now.Work in progress: