Blog Post: Introducing JobSet

[danielvegamyhre]

We would like to publish a blog post introducing JobSet, a K8s native API for distributed ML training and HPC workloads.

cc @ahg-g @kannon92 I think we still need to align on one example and ideally make it more concrete and polished. We should also explain the user story above it.

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	95ac8fd
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/6795206ba4e5380008256cb0
😎 Deploy Preview	https://deploy-preview-45759--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[kannon92]

/cc @haircommander

Trying to find an impartial reviewer ;)

[haircommander]

I have one note but I found this informative while doing a good job of laying the groundwork needed.

LGTM (assuming the note is unaddressable)

[sftim]

Some partial feedback (not yet a full review)

[sftim]

(if this is not yet ready for review by the blog team, please change the title to start with [WIP])

[sftim]

/hold

pending assignment of publication date

[danielvegamyhre]

(if this is not yet ready for review by the blog team, please change the title to start with [WIP])

Thanks Tim, added [WIP] to the title.

[sftim]

I propose the 26th of April as publication date. Does that work?

[sftim]

Let's pick a new publication date. How about the 7th of May?

[sftim]

You should remove [WIP] from the PR title @danielvegamyhre if / when you think this is ready to be reviewed.

[ahg-g]

/lgtm

Thanks @danielvegamyhre !

[danielvegamyhre]

@ahg-g I saw your comment that you were planning to clone and submit the PR registering the JobSet annotations/labels since the original author stopped responding. If that's done, we should merge this next.

[ahg-g]

What publication date should we target?

[sftim]

Let's go for 2015-01-10 - does that work?

[ahg-g]

yeah, that works

[danielvegamyhre]

Set publication date for 2025-01-13 since it was a few days til I had time to address these last comments, and want to give sufficient time for a final review.

[ahg-g]

The headers look strange, should we move this line up and use a bold font for the header?

[sftim]

IMO this is the right markdown

If the style doesn't look right: we'll take a PR (or you can file an issue).

Review was stale

[sftim]

@danielvegamyhre if you're comfortable rebasing, please rebase this against main; we've changed the site since this PR was first opened.

[sftim]

See #45759 (comment) about the proposed publication date.

[ahg-g]

@danielvegamyhre if you don't have time to address the remaining comments, I can take over the PR, please let me know.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: danielvegamyhre / name: Daniel Vega-Myhre (95ac8fd, 0ec6407)

[danielvegamyhre]

@ahg-g @sftim I addressed the latest comments and rebased on main. Excited to get this published!

[ahg-g]

Thanks Daniel!

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ahg-g
Once this PR has been reviewed and has the lgtm label, please ask for approval from sftim. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• content/en/blog/OWNERS

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

[ahg-g]

@sftim we missed the date; what new date do you suggest we put here?

[sftim]

Ah, sorry about that.

@danielvegamyhre can you add draft: true into the front matter and a new future & weekday publication date? Then we can merge it as a draft and the process to fix things up is simpler.

[danielvegamyhre]

Ah, sorry about that.

@danielvegamyhre can you add draft: true into the front matter and a new future & weekday publication date? Then we can merge it as a draft and the process to fix things up is simpler.

Sure, done. I chose Feb 3rd this time to give us some breathing room.

[ahg-g]

/lgtm
@sftim please take a look hopefully one last time

[sftim]

This PR needs more work.

If you're not sure how to check it, try:

# assumes a clean working directory with no uncommited changes etc
git fetch <remote> pull/45759/head:pr-45759
git switch main
make container-image
git pull --ff-only
git switch -c pr-45759-merge-preview
git merge pr-45759 --no-ff
make container-serve
xdg-open http://localhost:1313/blog # might just be "open" not "xdg-open"

and then you should have a new browser window showing a preview. Most edits show up live. You need a container runtime like Docker or Podman; see the Makefile for hints.
You can also do something similar on Windows, but we haven't yet documented how.

[sftim]

This doesn't render when I preview the article. I'm afraid that working images are a prerequisite for a merge.

Please consider using a figure short code with an alt attribute set.

[ahg-g]

Would replacing this block with the following work?

{{< figure src="jobset_diagram.svg" alt="JobSet Architecture" class="diagram-large" clicktozoom="true" >}}

or

![JobSet Architecture](jobset_diagram.svg)

[sftim]

/lgtm cancel
See #45759 (comment)

[ahg-g]

Would replacing this block with the following work?

{{< figure src="jobset_diagram.svg" alt="JobSet Architecture" class="diagram-large" clicktozoom="true" >}}

or

![JobSet Architecture](jobset_diagram.svg)

[ahg-g]

Suggested change

	<figure>
	<img src="jobset_diagram.svg">
	<figcaption><h4>JobSet Architecture</h4></figcaption>
	</figure>
	{{< figure src="jobset_diagram.svg" alt="JobSet Architecture" class="diagram-large" clicktozoom="true" >}}

[ahg-g]

can you please just apply the change?

[sftim]

I'm happy for someone to pick this up, but I really don't want to be the single load-bearing part in getting blog articles published. Because of how much I value distributing the work, I don't plan to do this step myself. @ahg-g you are welcome to ask other contributors to help out here.