-
Notifications
You must be signed in to change notification settings - Fork 893
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
[Kubeflow 1.9] Distributions and Kubeflow 1.9 #2611
Comments
@rimolive can you remove @DnPlas from Charmed Kubeflow and replace her with myself? ty! to your questions, for Charmed Kubeflow:
|
@rimolive deployKF will participate in 1.9, but it's not 100% clear exactly what that will look like. Separately, given "Kubeflow on AWS" did not participate in 1.8, and announced they were no longer supporting their distribution in awslabs/kubeflow-manifests#794, I think its unlikely they will do 1.9? Given this, I proposed moving them to "legacy" on the Kubeflow website on this PR kubeflow/website#3641. However, I also want to avoid confusion with users, because they might think that Kubeflow no longer supports AWS due to the "Kubeflow on AWS" name. So I also think we should merge kubeflow/website#3643 at the same time, which tells users that "Kubeflow on XXXX" is just a name, and NOT the ONLY way to use Kubeflow on that platform. |
For IBM IKS:
Yes
Yes |
For VMware Distro:
Yes
Yes |
For QBO Distro:
Yes
Yes |
For VMware Distro: Are you planning on having your distro ready in sync with the KF 1.9 release? Yes Will you participate by testing your distro during the distribution testing phase and providing feedback (reporting any issues to the release team)? Yes |
Calling all Distribution owners! I'm proud to announce our first Release Candidate for Kubeflow 1.9! You can find the release details in the following URL: https://github.com/kubeflow/manifests/releases/tag/v1.9.0-rc.0 We'll be working on another Release Candidate when we have Notebooks and KServe Models Webapp updated and ready for KF 1.9. We can use this issue to keep track of blocker issues for distributions while we work on fixing them. cc @ca-scribner @yhwang @johnugeorge @nagar-ajay @thesuperzapper @liuqi @xujinheng @alexeadem @alex-treebeard |
We also have to update cert-manager, knative, istio, seldon, bentoml etc which will come in later RCs. |
@ca-scribner @yhwang @johnugeorge @nagar-ajay @thesuperzapper @liuqi @xujinheng @alexeadem @alex-treebeard Can you please acknowledge that you are aware of Kubeflow 1.9 RC0 and are aware the the distributions testing phase has started? Please react with a thumbs up if everything is okay from your side and you are proceeding with testing. |
deployKF is mostly waiting on the updates from Notebooks (kubeflow/kubeflow#7453), but I am aware that a 1.9.0-RC0 was cut with other components. |
What do we mean by '(around 1.28)' here: https://github.com/kubeflow/manifests/tree/v1.9.0-rc.0?tab=readme-ov-file#prerequisites Is that v1.28.0 and v1.27.11? I'm proceeding with the testing in QBO.
Details:
In Kubernetes v1.28.0:
with NVIDIA GPU Operator
And Kustomize
as per kubeflow/pipelines#5285 So I used the following instead. I'll update the QBOT installer for this version This is what it was deployed
|
@alexeadem please check the updated release notes |
Hi @rimolive @StefanoFioravanzo, a couple of things:
|
Done
We decided to move on with rc0 because many components were upgraded, but there's a plan for rc1 with the remainder components. Is there one specific you are expecting to test? |
Just an update: We have just released Kubeflow 1.9.0-rc.1, which includes all updates from the Notebooks WG, Istio 1.18.7 (targetting to fully upgrade to 1.22 until the final release), and Model Registry 0.2.1-alpha. We ask all Distributions a help with testing the new release and open issues so we can work with the Working Groups to fix them until the final release. You can find the Release Notes in the releases page. cc @ca-scribner @DnPlas @yhwang @johnugeorge @nagar-ajay @thesuperzapper @liuqi @xujinheng @alexeadem @alex-treebeard |
Created an issue to track Nutanix distribution testing - nutanix/kubeflow-manifests#21 |
We are one week away from the Kubeflow 1.9.0-rc.2 release and we plan to be the last release candidate before final. We really welcome any updates about Distribution testing with bug reports, and anything that the release team should pursuit for rc.2 or final. cc @ca-scribner @DnPlas @yhwang @johnugeorge @nagar-ajay @thesuperzapper @liuqi @xujinheng @alexeadem @alex-treebeard |
We will start testing in the following two weeks, we'll keep you posted. |
Hello Distribution owners! Just wanted to announce Kubeflow 1.9.0-rc.2 release, it's the last one before we go final. Please take a look at the Release Notes here and help us validating the manifests by issuing a cc @ca-scribner @DnPlas @yhwang @johnugeorge @nagar-ajay @thesuperzapper @liuqi @xujinheng @alexeadem @alex-treebeard |
/lgtm
Recording: |
@liuqi @xujinheng Can you please confirm if you are testing Kubeflow 1.9.0-rc.2 manifests and let us know if it looks good? |
@yhwang Please let us know if you tested Kubeflow 1.9.0-rc.2 and it looks good. |
/lgtm verified the 1.9.0-rc.2 on IKS using the following settings:
|
Even better test the 1.9 branch in general because it will contain the final release https://github.com/kubeflow/manifests/commits/v1.9-branch/ and further fixes such as |
Yes, we are currently testing Kubeflow 1.9.0-rc2. Once we complete our testing, we will post the results here to keep you informed. |
/lgtm - verified workflows mentioned in the tracking issue. nutanix/kubeflow-manifests#21 |
As mentioned above, rc.2 does not contain all fixes. |
Failed to pull image "docker.io/kserve/models-web-app": no matching
manifest for linux/arm64/v8 in the manifest list entries
On a macbook with M3 CPU using `minikube start --cpus 8 --memory 8192
--kubernetes-version=v1.29 --driver=docker`
…On Wed, Jul 10, 2024 at 6:56 PM Julius von Kohout ***@***.***> wrote:
Yes, we are currently testing Kubeflow 1.9.0-rc2. Once we complete our
testing, we will post the results here to keep you informed.
As mentioned above, rc.2 does not contain all fixes.
—
Reply to this email directly, view it on GitHub
<#2611 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABX2CZFOXFEOWK5UNLQRQ3ZLUHNXAVCNFSM6AAAAABCLB22WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRQGE4TMNZSGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@tiansiyuan This thread is exclusively to track work with the Kubeflow Distribution owners to test 1.9 release. Please open an issue in https://github.com/kserve/models-web-app |
This is the current status of the Distribution Testing on July 10th:
We need your updates as quick as possible as our release date is July 22nd and in case of any bug reports we can take actions on time. |
kserve/models-web-app#88
Done.
…On Wed, Jul 10, 2024 at 9:26 PM Ricardo Martinelli de Oliveira < ***@***.***> wrote:
@tiansiyuan <https://github.com/tiansiyuan> This thread is exclusively to
track work with the Kubeflow Distribution owners to test 1.9 release.
Please open an issue in https://github.com/kserve/models-web-app
—
Reply to this email directly, view it on GitHub
<#2611 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABX2CYKY6XWR3YHUWWD4ODZLUZAJAVCNFSM6AAAAABCLB22WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRQGUYDQMZYGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hello, please retest with the 1.9 branch https://github.com/kubeflow/manifests/commits/v1.9-branch/ given the merge of #2795 Testing RC.2 is not enough. |
If no further bugs come up, i will synchronize any last-minute release tags from the other working groups on June 20-21 and do the change log and final release on July 22. @rimolive if i do not get any more final releases/tags from the other WGs, i probably have to release as is on july 22. You can also decide as release manager that we cut RC.3 and delay the final release. |
@juliusvonkohout hold on, we need the remaining WGs to cut their final releases. We cannot release 1.9 with components in RC releases. |
To cite myself from a few messages above: "if i do not get any more final releases/tags from the other WGs, i probably have to release as is on July 22. You can also decide as release manager that we cut RC.3 and delay the final release." I wont do anything today and when i am on vacation :-D As i said July 20-22 is when I can do the remaining stuff. |
This is the current status of the Distribution Testing on July 15th:
We had no changes in 5 days, and next week it's the Release date for 1.9. Please send us your updates so we can guarantee all Distributions are good with the release. |
@juliusvonkohout @rimolive @StefanoFioravanzo I have cut the final v1.9.0 tag for the |
Hey @rimolive, here is my latest update: version: 1.9.0-rc.2
So far it is looking good, so for that version /lgtm. |
Hello, This is the status for today July 22nd:
We see the majority of distributions agreed on the state of the release. Thank you so much for everyone involved in the testing. We'll keep receiving feedbacks for cases we can consider work on patch releases for 1.9. |
Is someone here encountering this bug/PR ? It has not been changed in 7 months https://github.com/kubeflow/manifests/commits/master/common/dex/base/config-map.yaml , but some users are complaining |
not in QBO |
This issue will be used to track the progress of and coordinate with distributions along the 1.9 release.
While we hope all distros will manage to be ready when the KF 1.9 release is out, this is sometimes difficult to achieve. In this issue, we want to both keep track of the progress of distributions towards the KF 1.9 release and also know which of the distros will be working on KF 1.9 (testing during the distribution testing cycle) even if they can't meet the KF 1.9 deadline.
Tagging distribution owners identified from previous releases (Any new or missed distro owners, please comment on this issue)
@zijianjoy
@Linchin
@yhwang
@nagar-ajay
@xujinheng
Please let us know if you'll be participating in the 1.9 release by answering the following questions:
Please note the release timelines are being discussed in #2606.
cc @kubeflow/release-team @jbottum
The text was updated successfully, but these errors were encountered: