Skip to content
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

create a list of Notebook features in Kubeflow 1.7 #6932

Closed
jbottum opened this issue Feb 2, 2023 · 8 comments
Closed

create a list of Notebook features in Kubeflow 1.7 #6932

jbottum opened this issue Feb 2, 2023 · 8 comments

Comments

@jbottum
Copy link
Contributor

jbottum commented Feb 2, 2023

/kind feature

Why you need this feature:
We need a list of features in 1.7 for the blog post and powerpoint presentation

Describe the solution you'd like:
The Notebook WG Team will provide a list of features and highlight breaking changes and top features.

@kimwnasptd

@kimwnasptd
Copy link
Member

kimwnasptd commented Feb 21, 2023

Hey @jbottum, sending here a first draft of the features/fixes list. @DomFleischmann this is also what we can use when cutting the final v1.7.0 tag in this repo, as release notes.

There are more PRs/commits that I didn't reference here, since I didn't want to just bump the full list of commits as the whole release notes. These are the most important IMHO. Will need to add the authors of the PRs in the release notes but we can do it at the end, before publishing the release.

What's new

What's fixed

Code health

@kimwnasptd
Copy link
Member

As I mentioned in the release team meeting one of the themes that we targeted with @orfeas-k and @elenzio9 was to work on how we expose information in the web apps. In KF 1.7 users will get:

  1. Sorting/filtering support in all the main tables of the apps
  2. Details pages for each notebook and volume
    • Users will also be able to navigate from one detail page to the other, by clicking object links (i.e. clicking on a mounted volume of a notebook will take you to the details page of that volume)
    • There will be logs, events, yaml info for each of these objects

Next steps for this effort will be to start working on allowing users to edit the objects themselves, now that we have such pages #6707 (comment).

@kimwnasptd
Copy link
Member

We also put a lot of effort with @apo-ger in this release to rework the GH Actions.

Now we are at the point where the actions:

  1. Build the images in each PR, of the affected components
  2. Deploy the manifests of the components
  3. Use the images that we just built in the deployed manifests

This means that in this release we are always testing that images can be deployed in each PR. Next steps here are to actually have more powerful integration tests, that will be using the deployed images. This is good because we are getting very close to testing in an environment similar to the final deployed stack

@kimwnasptd
Copy link
Member

Then another great effort in this release was from @surajkota where he put cycles and extended the whole TensorBoard stack we have, both the CRD and the web app, to allow use of PodDefaults (links above).

This will help us re-use the same mechanisms throughout the PodDefaults mechanism across the stack. And PodDefaults themselves got a boost in this release by supporting more use-cases (links above)

@kimwnasptd
Copy link
Member

Lastly, I think we should definitely highlight the effort for ppc64le support that @lehrig organized in #6684

It's really great to see efforts that will help Kubeflow getting more adoption in other platforms!

@lehrig
Copy link
Contributor

lehrig commented Feb 21, 2023

Lastly, I think we should definitely highlight the effort for ppc64le support that @lehrig organized in #6684

It's really great to see efforts that will help Kubeflow getting more adoption in other platforms!

Maybe something like this?

Enabled multi-arch builds for main Kubeflow components and KServe, adding ppc64le as supported processor architecture. See Phase 1 of #6684.

@juliusvonkohout
Copy link
Member

/close

@google-oss-prow
Copy link

@juliusvonkohout: Closing this issue.

In response to this:

/close

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.

Needs Triage automation moved this from To Do to Closed Oct 13, 2023
@kubeflow-bot kubeflow-bot removed this from Closed in Needs Triage Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants