Add KF 1.10 release blog post v1

[dpoulopoulos]

Add the Kubeflow 1.10 release announcement blog post.

[ederign]

/assign

[rimolive]

I would like to include a link for our survey

@dpoulopoulos Can you add the link to the survery? @ederign please share the url to us.

[ederign]

@rimolive I commented inline but it looks like https://github.com/kubeflow/blog/pull/166/commits/aeea0e8f6eaf266fce2dbc587efbf387c429979d was reverted. @dpoulopoulos can we add it again?

[dpoulopoulos]

@rimolive I commented inline but it looks like aeea0e8 was reverted. @dpoulopoulos can we add it again?

I see it's still there. Can't you see it?

[ederign]

@dpoulopoulos I just did a 'hard refresh,' and it appeared. Sorry for the noise.

@rimolive https://github.com/kubeflow/blog/blob/d582acd9bc528bbb4dcc60c91335fe121bdc720a/_posts/2025-03-26-kubeflow-1.10-release.md

[rimolive]

/lgtm

cc @kubeflow/kubeflow-steering-committee

[google-oss-prow[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: franciscojavierarceo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ~~OWNERS~~ [franciscojavierarceo]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[franciscojavierarceo]

😅 looks like this didn't have the hold on it like I thought it would. Sorry ab out that @andreyvelich we good here? I can revert it if we'd like.

[juliusvonkohout]

It is now live on the blog @franciscojavierarceo Probably it's better to just improve it iteratively in follow up PRs and then post it on our linkedin

[terrytangyuan]

Hmm there are some additional changes that are not part of this PR yet.

[terrytangyuan]

cc @StefanoFioravanzo

[thesuperzapper]

@franciscojavierarceo this is why people with root owner should not use the GitHub approval feature.

We do plan to fix it soon however, so that you have to use /approve explicitly to merge a PR.

[rimolive]

Personally I think we should begin with a plan to work with the WGs to provide updates about their work and publish in the blog.

Most of the blog posts are only Kubeflow releases, and not much updates about components/WGs. This would be benefitial to users who would like to know more about what's coming in future KF releases.

As for the PR approval/merge, I'm confident what we covered everything. After all, we started the work a month before the release date, and we had lots of reviews. If there's missing content, we should work on how I described before to have more content in the community blog.