The blog post: device failures handling

[SergeyKanzhelev]

Description

/sig node /cc @mrunalp

This is a blog post from the talk we gave on KubeCon NA 2024. Covers a lot of topics we will be working on in sig node and beyond this year in terms of reliability and extensibility.

[netlify[bot]]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	8f325240b07642e1a95b2a6dd5d9f555cac67a0b
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/67e5c8d1b423440007cdb60f
😎 Deploy Preview	https://deploy-preview-49333--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.

[SergeyKanzhelev]

@shannonxtreme I would appreciate any feedback on this.

[sftim]

There's a backlog on blog article reviews @SergeyKanzhelev and the blog team are going to prioritize the older articles for publication. We should have this published within a few months, maybe sooner.

[ffromani]

/cc (I'm interested on the topic)

[SergeyKanzhelev]

@sftim do you know how to enable the description list plugin? I got error when using {{% description-list %}}:

4:58:31 PM: Error: error building site: process: readAndProcessContent: "/opt/build/repo/content/en/blog/_posts/2025-01-14-devices-failure-handling/index.md:53:1": failed to extract shortcode: template for shortcode "description-list" not found

Trying this: https://kubernetes.slack.com/archives/C1J0BPD2M/p1738688053787199?thread_ts=1738687962.938049&cid=C1J0BPD2M

[sftim]

(you can use a ~CommonMark~ some de facto convention description list; no need to add a shortcode)

https://sebastiandedeyne.com/description-lists-in-markdown

[SergeyKanzhelev]

(you can use a ~CommonMark~ some de facto convention description list; no need to add a shortcode)

https://sebastiandedeyne.com/description-lists-in-markdown

this is how it rendered:

Am I doing it wrong?

[sftim]

Try a blank line before “Inference“, @SergeyKanzhelev

[sftim]

Also, nothing to do with Markdown, the inference work is often very quick, maybe as low as milliseconds or microseconds per evaluation, but the setup time to load the trained model can be minutes. You might want to capture that.

Language transformer models are a different beast but even these can do several tokens a second. What you wouldn't want to do is fire up a new instance per token (AWS Lambda style). Nope nope nope.

[SergeyKanzhelev]

Language transformer models are a different beast but even these can do several tokens a second. What you wouldn't want to do is fire up a new instance per token (AWS Lambda style). Nope nope nope.

I have this in the table. Good point!

[SergeyKanzhelev]

@sftim I believe I addressed all comments. Thank you for the review. What are the next steps?

[sftim]

@sftim I believe I addressed all comments. Thank you for the review. What are the next steps?

We're short on capacity for blog reviews with a lead time around 1 to 8 weeks. We hope to improve that lead time. Please hold.

[sanposhiho]

/cc

[sftim]

Thanks @sanposhiho for reviewing!

[sftim]

No need to hold as, if it merges, it will merge as draft (and then a small follow up PR would get it published).

/hold cancel

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: b42bea8d1bb32131484cc3cbcf99f1bf2cfef15b

[lmktfy]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ArangoGutierrez, lmktfy

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:

• ~~content/en/blog/OWNERS~~ [lmktfy]

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