-
Notifications
You must be signed in to change notification settings - Fork 49
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
DSPv2 #539
DSPv2 #539
Conversation
- Some components have conditions (only deploy if XYZ option set), so seperate these specific manifests from rest of the 'default ones for that component
- Some components have conditions (only deploy if XYZ option set), so seperate these specific manifests from rest of the 'default ones for that component
Dspv2 merge
A new image has been built to help with testing out this PR: To use this image run the following: cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines-operator.git
cd data-science-pipelines-operator/
git fetch origin pull/539/head
git checkout -b pullrequest cd786d97ebdbca735a76a11891df824d4a448419
make deploy IMG="quay.io/opendatahub/data-science-pipelines-operator:pr-539" More instructions here on how to deploy and test a Data Science Pipelines Application. |
/hold |
There's a DSPA failing with How to reproduceCheck out this branch: gh pr checkout 539 On a fresh cluster, deploy Argo: oc new-project argo
make argodeploy Create the oc new-project opendatahub Deploy DSPO from the branch: make deploy IMG="quay.io/opendatahub/data-science-pipelines-operator:pr-539" Create the oc new-project kubeflow Checkout https://github.com/hbelmiro/data-science-pipelines-operator/tree/issue-498: gh pr checkout 541 Deploy the DSPA to the kustomize build config/samples/v2/custom-configs | oc -n kubeflow create -f - Get the route for the DSPA: oc get route ds-pipeline-ui-sample -n kubeflow Open the URL in the browser and start a new pipeline run. In the pipeline run view, you'll see the error message after a few seconds. |
Document supported Argo versions for v2
Change to PR detected. A new PR build was completed. |
I retested this on a couple clusters, one of which was freshly provisioned, and wasn't able to reproduce the problem. I did notice that the error message was shown on the run when first kicked off, but it very quickly resolved on its own, and i believe had to do with creating the run so soon after DSPA creation. |
/lgtm |
/hold let's make sure this merged while everyone is awake / around |
/unhold |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amadhusu, gregsheremeta, hbelmiro 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 |
The issue resolved by this Pull Request:
Resolves #534
Description of your changes:
Merge in dspv2 feature branch
Testing instructions
Full Testing suite required. Deploy DSPO, ensure sanity. Deploy v1 and v2 DSPAs
Checklist