chore: Add kfp-tekton integration tests and manifests

[rimolive]

Description of your changes:
Solves #10489

Adds the kfp-tekton integration tests and corresponding manifests

Checklist:

• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[rimolive]

/hold

Wait for tests to pass before ask for review/approval

[Tomcli]

few comments on the registry name.

[rimolive]

Test are failling because some resources don't have namespace explicitly set. Some examples:

• MySQL
• ml-metadata Envoy Proxy
• ml-metadata gRPC Server

I tried to find a way to set in the kustomization.yaml level to set namespace in the objects that don't have namespace set but no luck. That being said, I'd like to ask @Tomcli and @chensun :

• Is it ok if I set namespace in these Deployments?
• If not, do you suggest another way to make them deploy in kubeflow namespace without explicitly setting in these objects?

[Tomcli]

few comments on fixing the old kustomize code to kustomize 5.2.1

[Tomcli]

Also, I think you didn't copy some role permission from the persistent agent, so the end to end test wasn't able to update the run status.

https://github.com/kubeflow/kfp-tekton/blob/v2-integration/manifests/kustomize/base/pipeline/ml-pipeline-persistenceagent-role.yaml#L29-L45

[rimolive]

Also, I think you didn't copy some role permission from the persistent agent, so the end to end test wasn't able to update the run status.

https://github.com/kubeflow/kfp-tekton/blob/v2-integration/manifests/kustomize/base/pipeline/ml-pipeline-persistenceagent-role.yaml#L29-L45

Thank you for that! I'm still trying to figure you why the flip coin pipeline never finishes. At least with that change I can see the pipeline status of RUNNING, but it stays in that status until failure.

[rimolive]

Just a checkpoint comment: Tests are passing, but I still need to address Tommy's comment on Kustomize 5.2.1 support and the re-tag script.

[rimolive]

/unhold
cc @Tomcli @chensun

[DharmitD]

Skimmed through the integration test results in CI and verified they work as expected.

/lgtm

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chensun

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 [chensun]

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

[rimolive]

@chensun Looks like e2e test did not finish well, but unrelated to the PR. Should we try run again?

[rimolive]

/test kubeflow-pipeline-e2e-test