-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
fix(backend): updated the argo version too 2.7.7. Fixes #4392 #4498
Conversation
github.com/Masterminds/squirrel v0.0.0-20190107164353-fa735ea14f09 | ||
github.com/VividCortex/mysqlerr v0.0.0-20170204212430-6c6b55f8796f | ||
github.com/argoproj/argo v2.3.0+incompatible | ||
github.com/argoproj/argo v0.0.0-20200506223611-54154c61eb4f |
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.
Is it possible to use a release version here?
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.
Not sure, will check if possible.
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 answer seems to be no, @Ark-kun argoproj/argo-workflows#2602 (comment)
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 meant to ask whether it' possible to refer to particular GIT tag like github.com/argoproj/argo v2.7.5...
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 will try to clean this up after I fixed some of the bugs :)
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 don't get it to work to specify the version as you mention @Ark-kun, agree that it would be better to have it with version.
This would be great! Can you fix the build failure? |
@@ -263,7 +263,8 @@ spec: | |||
arguments: {} | |||
entrypoint: rand-fail-dag | |||
templates: | |||
- dag: | |||
- arguments: {} |
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.
Hmm. I thought this Argo issue was fixed at some point...
Update: Turns out, not fully argoproj/argo-workflows#1686
Working on it :) |
/test kubeflow-pipeline-backend-test |
I have been manage to fix some of the issues but still getting issues with the integration tests according to automatic tests. When runing the tests locally using bazel, I get the following issue:
As I understand this is related to the CRD client, however when trying to update it seems like the file for updating the API,
Is this still the supported way to update the client? I am a bit on deep water would be great if you could point me in the right direction @neuromage, @Bobgy |
@NikeNano Great progress! For
I think you can run However, I believe no one has tried to rerun it again for a while, so it's totally possible something will fail. Feel free to report it back here. |
From the main folder(
Inside
and thus it seems like the |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
Thank you so much! All looking good now! /lgtm |
I think you used a different email account to do one of the commits, overriding the cla for you. |
By the way, is this argo client 2.7.5? |
/hold |
/unhold
The argo package is updated to version 2.7.7 removed client from the name of the PR as well. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Bobgy, NikeNano 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 |
Argo supports a field in the ResourceTemplate that makes the controller add an owner reference of the workflow to the created resource since v2.4.0 [1]. With the upgrade of Argo client [2] and deployment [3] we are now able to exploit it. We set it to 'false' by default on all ResourceOps (actually, leave it empty) and 'true' for VolumeOps. This allows the garbage collection of PVCs upon workflow cleanup without any further change [4]. [1] https://github.com/argoproj/argo/blob/v2.4.0/pkg/apis/workflow/v1alpha1/workflow_types.go#L1044-L1045 [2] kubeflow#4498 [3] kubeflow#3537 [4] kubeflow#1779 Signed-off-by: Ilias Katsakioris <elikatsis@arrikto.com>
…ow#1779 Argo supports a field in the ResourceTemplate that makes the controller add an owner reference of the workflow to the created resource since v2.4.0 [1]. With the upgrade of Argo client [2] and deployment [3] we are now able to exploit it. We set it to 'false' by default on all ResourceOps (actually, leave it empty) and 'true' for VolumeOps. This allows the garbage collection of PVCs upon workflow cleanup without any further change [4]. [1] https://github.com/argoproj/argo/blob/v2.4.0/pkg/apis/workflow/v1alpha1/workflow_types.go#L1044-L1045 [2] kubeflow#4498 [3] kubeflow#3537 [4] kubeflow#1779 Signed-off-by: Ilias Katsakioris <elikatsis@arrikto.com>
…kubeflow#4498) * updated the version * updated the serializer * fixed test * fixed some more changes * tested to update versions of k8 packages * reverted package update * change in API * fixed dependencies, need to fix broken tests now * updated fake client and fixed test due to updates in timestam.timestamp * missed to update fake client pod * fixed issue in controller * tested to update * updated * updated controller viewer * updates to fix go mod vendor * Updated the client * updated the golang versions * missed one docker file update, from 1.11 -> 1.13 * testing to fixe persistinace agent issues * Updated after feedback Co-authored-by: Niklas hansson <niklashansson@Niklass-MacBook-Pro.local>
…ow#1779 Argo supports a field in the ResourceTemplate that makes the controller add an owner reference of the workflow to the created resource since v2.4.0 [1]. With the upgrade of Argo client [2] and deployment [3] we are now able to exploit it. We set it to 'false' by default on all ResourceOps (actually, leave it empty) and 'true' for VolumeOps. This allows the garbage collection of PVCs upon workflow cleanup without any further change [4]. [1] https://github.com/argoproj/argo/blob/v2.4.0/pkg/apis/workflow/v1alpha1/workflow_types.go#L1044-L1045 [2] kubeflow#4498 [3] kubeflow#3537 [4] kubeflow#1779 Signed-off-by: Ilias Katsakioris <elikatsis@arrikto.com>
…ow#1779 Argo supports a field in the ResourceTemplate that makes the controller add an owner reference of the workflow to the created resource since v2.4.0 [1]. With the upgrade of Argo client [2] and deployment [3] we are now able to exploit it. We set it to 'false' by default on all ResourceOps (actually, leave it empty) and 'true' for VolumeOps. This allows the garbage collection of PVCs upon workflow cleanup without any further change [4]. [1] https://github.com/argoproj/argo/blob/v2.4.0/pkg/apis/workflow/v1alpha1/workflow_types.go#L1044-L1045 [2] kubeflow#4498 [3] kubeflow#3537 [4] kubeflow#1779 Signed-off-by: Ilias Katsakioris <elikatsis@arrikto.com>
…ow#1779 Argo supports a field in the ResourceTemplate that makes the controller add an owner reference of the workflow to the created resource since v2.4.0 [1]. With the upgrade of Argo client [2] and deployment [3] we are now able to exploit it. We set it to 'false' by default on all ResourceOps (actually, leave it empty). Setting the field to 'true' for VolumeOps allows the garbage collection of PVCs upon workflow cleanup [4]. [1] https://github.com/argoproj/argo/blob/v2.4.0/pkg/apis/workflow/v1alpha1/workflow_types.go#L1044-L1045 [2] kubeflow#4498 [3] kubeflow#3537 [4] kubeflow#1779 Signed-off-by: Ilias Katsakioris <elikatsis@arrikto.com>
…ow#1779 Argo supports a field in the ResourceTemplate that makes the controller add an owner reference of the workflow to the created resource since v2.4.0 [1]. With the upgrade of Argo client [2] and deployment [3] we are now able to exploit it. We set it to 'false' by default on all ResourceOps (actually, leave it empty). Setting the field to 'true' for VolumeOps allows the garbage collection of PVCs upon workflow cleanup [4]. [1] https://github.com/argoproj/argo/blob/v2.4.0/pkg/apis/workflow/v1alpha1/workflow_types.go#L1044-L1045 [2] kubeflow#4498 [3] kubeflow#3537 [4] kubeflow#1779 Signed-off-by: Ilias Katsakioris <elikatsis@arrikto.com>
…4831) Argo supports a field in the ResourceTemplate that makes the controller add an owner reference of the workflow to the created resource since v2.4.0 [1]. With the upgrade of Argo client [2] and deployment [3] we are now able to exploit it. We set it to 'false' by default on all ResourceOps (actually, leave it empty). Setting the field to 'true' for VolumeOps allows the garbage collection of PVCs upon workflow cleanup [4]. [1] https://github.com/argoproj/argo/blob/v2.4.0/pkg/apis/workflow/v1alpha1/workflow_types.go#L1044-L1045 [2] #4498 [3] #3537 [4] #1779 Signed-off-by: Ilias Katsakioris <elikatsis@arrikto.com>
Description of your changes:
Fixes #4392
Checklist:
Do you want this pull request (PR) cherry-picked into the current release branch?
Learn more about cherry-picking updates into the release branch.