-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Extend e2e-tests: Add resources tests #1342
Conversation
/ok-to-test |
/test kubeflow-pipelines-e2e-test |
/cc @IronPan @gaoning777 |
b324cd1
to
c47e3a3
Compare
Due to Also, I have to cherry-pick kubeflow/kubeflow#2556 into |
Could you take a look at kubeflow/kubeflow#3293 ? |
@elikatsis, I'd suggest to change resourceop basic sample to demonstrate a more realistic use case like what argo sample does: create a k8s job. It doesn't seem right to expose cluster wide secret create/delete permissions for pipeline runner. You may optionally demo pvolume usage by orchestrating it with a job spec, which will be very useful sample to answer question like #1345. WDYT? |
@hongye-sun I can add a sample with some |
* Change Argo version deployed from v2.2.0 to v2.3.0-rc3 * Add resourceop test: Executes the resourceop_basic.py Extend run_basic_test.py with '--params' argument. * Add volumeop test: Executes the volumeop_sequential.py pipeline * Change modes from RWM to RWO for VolumeOp in volumeop_sequential.py * We cannot use some other sample with VolumeOps because GCP does not support the ReadWriteMany access mode. We also cannot use a VolumeSnapshotOp sample, because VolumeSnapshots only exist in Alpha GCP clusters. Signed-off-by: Ilias Katsakioris <elikatsis@arrikto.com>
Signed-off-by: Ilias Katsakioris <elikatsis@arrikto.com>
c47e3a3
to
c621a50
Compare
test/deploy-kubeflow.sh
Outdated
@@ -56,4 +56,11 @@ ${KUBEFLOW_SRC}/scripts/kfctl.sh apply platform | |||
${KUBEFLOW_SRC}/scripts/kfctl.sh generate k8s | |||
${KUBEFLOW_SRC}/scripts/kfctl.sh apply k8s | |||
|
|||
pushd ks_app |
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.
do you think we can bump the version in kfctl instead?
https://github.com/kubeflow/kubeflow/blob/master/kubeflow/argo/prototypes/argo.jsonnet
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.
Sure, I saw kubeflow/kubeflow#3335 so I pushed the removal of these lines, along with the corresponding change in test/install-argo.sh
.
Let's merge this upon the aforementioned PR's approval. Would that be ok?
Signed-off-by: Ilias Katsakioris <elikatsis@arrikto.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: hongye-sun If they are not already assigned, you can assign the PR to them by writing 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 |
/test kubeflow-pipeline-e2e-test |
Would you mind checking the errors? It must be something regarding the deletion of the deployment. |
/retest |
@IronPan, do you know any known test issue recently? |
Looks like leaking resources have used up all the quota. /test kubeflow-pipeline-e2e-test |
Cool, it seems it got fixed and the tests succeeded |
@Ark-kun you said leaking resources, is there something we could do to the tests to prevent it? |
/test kubeflow-pipeline-sample-test |
/hold |
/retest |
Generally LGTM, but the test probably belongs to sample tests. We've recently upgraded sample_test.yaml and it's now easier to add more tests. |
@Ark-kun: GitHub didn't allow me to request PR reviews from the following users: gaoning777. Note that only kubeflow members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
@elikatsis: The following test 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. |
Closing this since testing has changed a lot. I opened #2019 to cover a part of it and more PRs will follow. |
I think we should start moving to v2.3 already by using the latest pre-release (v2.3.0-rc3). It comes with a lot of features and bug fixes.
This way:
I'm sure there are more stuff we can take advantage of. But also, we can start deprecating stuff such as the global
volumes
attribute, to use template-local volumes instead.I have been using this release extensively and it seems to be working fine.
I'm making this PR to run the E2E tests. I set the deployment scripts accordingly to deploy Argo v2.3.0-rc3.
Then, if all tests are successful, I suggest to update the kubeflow repo's argo deployment, since 0.1.20 release totally covers #1250.
WDYT?
/cc @Ark-kun @vicaire @hongye-sun
If everything works this PR closes #1250.
This change is