blog: PodLogsSplitStreams announcement

[knight42]

Description

Add a blog post about the new introduced pod logs split streams feature.

Issue

Ref kubernetes/enhancements#3288

[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 assign nate-double-u for approval. 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

[knight42]

/cc @edithturn

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	fe6dddc
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/672263b5ff359b0008ef3456
😎 Deploy Preview	https://deploy-preview-48598--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.

[mbianchidev]

Hey hey,
it's Matteo here, Comms Lead for 1.32

When will this piece be ready for review?
Reminder that the review deadline is on the 25th of November.

Let us know if you need something from us, otherwise we will just mark it as ready for review and have sig-docs-blogs review it for content and the assigned SIG to chime in for a tech review.

Thank you!

[knight42]

Hi Matteo, the current state is quite weird. Since the kubectl PR doesn't get merged, this feature is kinda incomplete without kubectl, so I am not entirely sure what to do.

[mbianchidev]

@knight42 unfortunately I'm not sure about how the kubectl release cycle works but I would suggest that this blog can fall off the 1.32 cycle overseeing and be treated as a standard k8s blog instead.

This is because it seems like it's not tightly tied to the 1.32 release and could be merged at a later phase without impacting it.

Let me know if you have any question!

EDIT: blog fell off the release 1.32 cycle, can be treated as standard blog

[mbianchidev]

Info for SIG Docs (blog) - this blog fell off the release cycle, it can still be merged as a standard blog (in case the author communicates the blog is ready for submission) but it's not as prioritized as the ones currently tracked in the Comms board for 1.32

Thank you!