Pipelines WG and Kubeflow 1.5 release

[kimwnasptd]

@zijianjoy let's use this tracking issue to coordinate the integration of Pipelines with the Kubeflow 1.5 release.

First off a heads up that the feature freeze phase will start Tuesday (25th January). Before then I'd like to have updated this repo with the manifests of the kubeflow/pipelines repo, in order to be able to cut the first RC tag in this repo.

So what I'd like to ask as a first step before the feature freeze is:

• What version of KFP would you like to include for the 1.5 release?
• Could you provide me with a branch/tag for this version? It doesn't have to be final. The branch/tag provided can keep on getting fixes through out the release process, but not new features
• Are there any open issues/work in progress that you will be working on for your version as the KF release process will be progressing?
• What will the K8s supported versions be for kubeflow/pipelines?

cc @kubeflow/wg-pipeline-leads
cc @kubeflow/release-team

[kimwnasptd]

From the versioning issue we had we know we are targeting 1.8.0 #2098 (comment). @zijianjoy let's use this issue for further updates, new tags, progressing issues etc.

[zijianjoy]

Thank you Kimonas,

• We are planning to use KFP 1.8.0 in this release.
• You can use the RC here: https://github.com/kubeflow/pipelines/releases/tag/1.8.0-rc.1
• I am looking for a list of all Kubeflow components' versions so I can test the full-fledged Kubeflow integration, where can I get such information?
• KFP is planning to support k8s 1.22

[kimwnasptd]

Awesome thanks for the info! I'll use this tag to update the manifests.

I am looking for a list of all Kubeflow components' versions so I can test the full-fledged Kubeflow integration, where can I get such information?

We are gathering this information for each WG, in their respective issues. But I'll also try to have this information in one place #2112

[annajung]

Hi @zijianjoy, Before the manifest testing on Wednesday, Feb 9th, the release team is planning on cutting another RC to use for the testing.

Based on a previous communication, the release team will be using KFP version 1.8.0-rc.1. If the pipeline WG have identified any issues since the feature freeze and would like to update the pipeline version before the manifest testing, let us know before Feb. 9th. Thank you!

[zijianjoy]

Hello @annajung , we are expecting some cherry-pick for fixes only in kubeflow/pipelines#7263. We are still working on the new release candidate. I will update you once we have a new release candidate.

[annajung]

Hi @zijianjoy, looks like 1.8.0-rc.2 is available now. Could you confirm that that's the right one to be used for the next 1.5 RC?

[zijianjoy]

@annajung Hello Anna, that is right, please use this KFP RC for Kubeflow 1.5 RC

[imiller445]

Hi, we are testing the 1.5 release candidates, specifically looking at KFP support for k8s 1.22. During the install we found that metacontroller is still using apiextensions.k8s.io/v1beta1 for its CRDs. I apologize, I'm not intimately familiar with the KFP lay of the land. Is this something that would need to be upgraded for k8s 1.22 support or is it considered not core to KFP?

[zijianjoy]

It shouldn't be the case. You can see CRD from this file https://github.com/kubeflow/pipelines/blob/master/manifests/kustomize/third-party/metacontroller/base/crd.yaml. Have you tried the latest release candidate of KFP backend 1.8.0?

[imiller445]

Ah, thanks @zijianjoy ! I was going off of the 1.5 release candidate tag on the kubeflow/manifests repo: https://github.com/kubeflow/manifests/blob/v1.5.0-rc.0/apps/kfp-tekton/upstream/third-party/metacontroller/base/crd.yaml

I'll repoint my kfp-tekton kustomize to the link you sent and that looks like it ought to do it. Appreciate the reply!

[kimwnasptd]

Heads up, I'm going to update the KFP component to the new stable 1.8.1 version

cc @kubeflow/release-team

[shannonbradshaw]

Hey, folks. Are there docs changes required as a result of this work? If so, please create an issue and mention in on this docs tracking issue: kubeflow/website#3130

[juliusvonkohout]

/close

There has been no activity for a long time. Please reopen if necessary.

[google-oss-prow]

@juliusvonkohout: Closing this issue.

In response to this:

/close

There has been no activity for a long time. Please reopen if necessary.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.