Add support for dsl.ResourceOp

[fenglixa]

Which issue is resolved by this Pull Request:
Resolves #49

Description of your changes:

Based on kubectl-wrapper, we have following parameters in Tekton task right now, which are used for supporting Tekton resourceOps:

• action: -- the action to perform to the resource
• merge_strategy: -- the strategy used to merge a patch, defaults to "strategic"
• success_condition: a label selector expression which describes the success condition
• failure_condition: a label selector expression which describes the failure condition
• manifest: the kubernetes manifest
• output: An express to retrieval data from resource, all the output will be writen to tekton/result/output file.
• set-ownerreference: Enable set owner reference for created resource, just leave interfaces there.

@vincent-pli , I think the code of kubectl-wrapper should be committed to kfp-tekton as well, to support more features in future, or any bug fixes.

[kubeflow-bot]

This change is 

[fenglixa]

/cc @animeshsingh

[Tomcli]

Great job @fenglixa, overall the compiler side looks very good. I will also take a look at the actual task and give some comments over there.

[Tomcli]

We probably need to have some instructions for adding certain rbac permission to this pipeline. I will open an issue and do it in a different PR.

[animeshsingh]

Thanks @fenglixa - great job!

I think the code of kubectl-wrapper should be committed to kfp-tekton as well, to support more features in future, or any bug fixes.

Isn't the wrapper going in Tekton repo?

[fenglixa]

Thanks @Tomcli , I addressed you comments, please help review whether it's OK for you now.

[fenglixa]

Isn't the wrapper going in Tekton repo?

I discussed it with @vincent-pli before. It's better the wrapper could be going to Tekton repo, but seems it could be only going as Tekton catalog.
Personaly, we should find a location in kfp-tekton, to let the wrapper code there, convenient for us to maintain and add new features, how do you think? @animeshsingh .

[Tomcli]

Thanks @fenglixa, it works well with the basic resourceOp example. However, the output only takes one argument where volumeOp and volumeSnapShotOp is expecting 3. Probably we need to enhance the output argument to output a list of results instead of a single output file. It's better to enhance the wrapper for that feature.

Although I do love to merge what we have now, so we can start work on the new features for volumeOp and volumeSnapShotOp in parallel.

/lgtm

[Tomcli]

@fenglixa So after some discussion with Animesh, we probably should push the warpper code to tektoncd/catalog because kfp-tekton shouldn't maintain any custom Tekton image. Also this way we can get more feedbacks from the tekton community. What do you think?

[fenglixa]

So after some discussion with Animesh, we probably should push the warpper code to tektoncd/catalog because kfp-tekton shouldn't maintain any custom Tekton image. Also this way we can get more feedbacks from the tekton community. What do you think?

It's OK to me. Thanks.

[animeshsingh]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: animeshsingh

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:

• OWNERS [animeshsingh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment