-
Notifications
You must be signed in to change notification settings - Fork 220
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
Data WG roadmap for KF 1.10 #769
Comments
from Model Registry WG
|
From Spark Operator: |
We need a maintainer for the spark manifests at https://github.com/kubeflow/manifests/tree/master/contrib/spark. See also https://github.com/kubeflow/manifests/blob/master/proposals/20220926-contrib-component-guidelines.md#component-requirements for PSS restricted requirements and there should be a synchronization script in /hack even if it just resembles the current makefile |
/assign @milosjava |
not using a specific version, usiing from platform wg |
@milosjava to follow up on this |
Model registry , no red flags , blockers…. |
Model Registry no blockers, we can say that approx 50% is done. As Josh suggested on a community call we will find an end-user and go through docs together. My idea for the end user is one of our (pepsico) projects. Regarding SparkOperator and the follow up:
To summarize: Smoke test, security stance, Kustomize and doc work are doable. Need more info on Integration between the operator and Kubeflow |
Also I think would be possible to find end-user for SparkOperator as well. |
Spark-operstor is already in our CICD. Here are the remaining issues to promote it to an application kubeflow/manifests#2912 |
@rimolive Sharing model registry progress track: https://github.com/kubeflow/model-registry/milestones |
UI road map : kubeflow/model-registry#175 (comment) |
from Milos in Release meeting:
|
We need to follow up on this @milosjava any updates |
Model Registry, still in green, no blockers. current focus on kubeflow/model-registry#599 |
@milosjava mentions in the Release meeting:
|
Model Registry progressing, no issues. Spark Operator: seems there is an issue with integration with Kubeflow. I am in the contact with number of Spark Operator developers and it seems istio support is problem and probably we need help with this. More info: kubeflow/manifests#2912 (comment) |
Hello @kubeflow/wg-data-leads @tarilabs @ChenYi015
The 1.10 release team will use this tracking issue to coordinate the integration of the Model Registry and Spark Operator with the Kubeflow 1.10 release.
Heads up that the feature freeze is scheduled for January 20th 2025 (needs confirmation). For the full release schedule, refer to the 1.10 release timeline.
(note: links are pending due to #761)
To prepare for the 1.10 release, please provide answers to the following questions:
The release team WG liaison for Pipelines WG will be @milosjava and you can keep track of high-level release updates in the #768 issue.
The text was updated successfully, but these errors were encountered: