-
Notifications
You must be signed in to change notification settings - Fork 875
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
Manifests WG KF 1.9 tracker #2592
Comments
Hello @juliusvonkohout , this is a kind reminder that Monday, March 4th will be our Kubeflow 1.9 release development checkpoint, we will be halfway through our dev cycle, and we expect most of the work to be well underway (reminder: code freeze is scheduled for Apr 15th) Can you please acknowledge your status with respect to the manifests roadmap, comment on the progress made so far, and provide an assessment of the work that remains? The comment above includes a lot of work streams, part of which are probably related to the Security Working Groups. Can you please update the comment to list only the work that pertains to the Manifests, and clearly call out what's already completed and what remains to be done? |
@StefanoFioravanzo i updated the top post, but the development is still ongoing. |
@StefanoFioravanzo @rimolive i added lots of stuff and it should be more clear now what is left for 1.9.0 rc1 |
@juliusvonkohout can we close this issue? I guess we are tracking any active item in #2763 |
Yes i will close, but our shiny new stalebot would do so as well :-) |
Let's use this issue to track work items for Manifests WG and KF 1.9
follow up of #2456
See also #2613 for version tracking
and security stuff implemented in the manifests repository #2598
More work on
/contrib
componentsFurther improvements on both tooling and health of manifests
Oauth2-proxy and JWT
Kustomize 5 work
This is just an initial list based on ongoing efforts. Feel free to propose more work items that you are interested in driving to include them as part of our planning
cc @kubeflow/wg-manifests-leads @kimwnasptd
GSOC for 1.10 probably :
The text was updated successfully, but these errors were encountered: