Update kubeflow/pipelines manifests from 2.0.5

[rimolive]

Which issue is resolved by this Pull Request:
Resolves #

Description of your changes:

Checklist:

• Unit tests pass:
  Make sure you have installed kustomize == 5.0.3
  1. make generate-changed-only
  2. make test

[juliusvonkohout]

The git diff looks empy which is good
/manifests/apps/pipeline/upstream$ git diff /home/julius/Downloads/pipelines-2.0.5/manifests/kustomize .
but there are two topics:

1. updating kfp-tekton to 2.0.5
2. fixing the integration tests. ill just try a rerun for now.

I will add a script to apps/pipeline to automate the manifest synchronization.

[juliusvonkohout]

Lets use #2625 for updates

[juliusvonkohout]

Maybe you need to cherry pick some test fixes from #2544

[rimolive]

@chensun Need your help here. This PR is crucial to release Kubeflow 1.8.1.

Integration test is falling because of something related to cert-manager. Can you take a look?

[juliusvonkohout]

@rimolive this has to be merged to master as well. Usually we start with Master and cherry pick to the 1.8 branch.

[chensun]

@chensun Need your help here. This PR is crucial to release Kubeflow 1.8.1.

Integration test is falling because of something related to cert-manager. Can you take a look?

Cert-manager was introduced by Amazon folks, my understanding is they should only apply to AWS deployment.
@surajkota Can you help take a look? Thanks!

[juliusvonkohout]

cert-manager is used by default. Sometimes it just does not become ready fast enough. a wait for cert-manger as done here might help.

manifests/tests/gh-actions/install_cert_manager.sh

Line 10 in a9ff8eb

kubectl wait --for=jsonpath='{.subsets[0].addresses[0].targetRef.kind}'=Pod endpoints -l 'app in (cert-manager,webhook)' --timeout=180s -n cert-manager

[juliusvonkohout]

@rimolive i pushed 0d53c9e please rebase

[juliusvonkohout]

Now we get

Traceback (most recent call last):
  File "/home/runner/work/manifests/manifests/./tests/gh-actions/kf-objects/test_pipeline.py", line 6, in <module>
    @comp.create_component_from_func
AttributeError: module 'kfp.components' has no attribute 'create_component_from_func'. Did you mean: 'load_component_from_file'?
Error: Process completed with exit code 1.

[juliusvonkohout]

https://github.com/kubeflow/manifests/blob/master/tests/gh-actions/kf-objects/test_pipeline.py must be adjusted or we downgrade pip3 install kfp==2.7.0 to 1.8.22

[juliusvonkohout]

@rimolive Somewhere around here

manifests/.github/workflows/pipeline_kind_test.yaml

Lines 42 to 46 in 8f76ccb

	./tests/e2e/hack/proxy_pipelines.sh
	kubectl apply -f tests/e2e/yamls
	python3 ./tests/gh-actions/kf-objects/test_pipeline.py
	./tests/gh-actions/install_argo_cli.sh
	argo wait @latest -n kubeflow-user-example-com --request-timeout 60

it is failing

Maybe the timeout is too tight, but i would really like to drop this outdated argo file and test and just check the workflow status directly with kubectl

[juliusvonkohout]

@rimolive i need access to your branch to sign my commits. You can also sign them if you want.

[juliusvonkohout]

Why did you revert my fix for KFP 2.7.0 to 1.8.22? We can stay on the 1.8.22 SDK. V2 pipelines are still on a beta level. Or at least we should test v1 and V2 pipelines.

[rimolive]

Sorry, I did not notice you added that commit. Can you send it again?

[juliusvonkohout]

It is just replacing the value 2.7.0 with 1.8.22

[juliusvonkohout]

Ok we have to increase the timeout i guess, but that is something for the master branch.

[juliusvonkohout]

/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: juliusvonkohout, rimolive
Once this PR has been reviewed and has the lgtm label, please assign stefanofioravanzo for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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