[WIP] 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[bot]]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	d3d0821871bc7d6e88fc932d96342c1ea89f7db5
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/66590787b28a48000881c1a9
😎 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]

(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 !

[sftim]

LGTMs from https://github.com/kubernetes/website/pull/45759#issuecomment-2032989002 and https://github.com/kubernetes/website/pull/45759#issuecomment-2142709135 mean that all this needs is a new publication date.

Sorry about the wait; we have very few active blog reviewers.

I suggest aiming for the 17th of July; does that work?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please ask for approval from sftim. For more information see the Kubernetes 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

[sftim]

Content LGTMs noted, but publication date does need to change.

/lgtm cancel

[sftim]

There's a long disagreement over whether it's OK to publish this, given it would tacitly bless using annotations the wrong way (the JobSet controller looks for annotations and labels that look Kubernetes official, but aren't yet on our list of known annotations).

I'm personally loth to publish this without settling that disagreement. Making an exception once has me thinking it could set a precedent we end up having to live with.

[danielvegamyhre]

There's a long disagreement over whether it's OK to publish this, given it would tacitly bless using annotations the wrong way (the JobSet controller looks for annotations and labels that look Kubernetes official, but aren't yet on our list of known annotations).

I'm personally loth to publish this without settling that disagreement. Making an exception once has me thinking it could set a precedent we end up having to live with.

I'm fine with registering the annotations before publishing

[danielvegamyhre]

Update: we are close to merging the PR registering JobSet labels/annotations (https://github.com/kubernetes/website/pull/47383). Once that is done we can move forward with publishing the blog post here.