Feature Blog placeholder PR for 1.36: Userns goes GA

[rata]

Hi! I'd like to do a feature blog for 1.36, as userns is going GA. Is this the right way to do it?

cc @giuseppe @saschagrunert @haircommander

Description

Issue

Closes: #

[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 lmktfy for approval. For more information see the Code Review Process.

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

Details

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

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	56445ee
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/698b312691b06d0008d9278b
😎 Deploy Preview	https://deploy-preview-54370--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 project configuration.

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	338f78c
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/698b319f0b72a50008324388
😎 Deploy Preview	https://deploy-preview-54370--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 project configuration.

[lmktfy]

Hi! I'd like to do a feature blog for 1.36, as userns is going GA. Is this the right way to do it?

The blog team recommend starting with either HackMD or a Google Doc. If you'd like to follow up on Slack, the people to approach are #release-comms and #sig-docs-blog.

[chadmcrowell]

/label sig-release

[k8s-ci-robot]

@chadmcrowell: The label(s) /label sig-release cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label sig-release

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[rata]

/label-sig sig-release

@chadmcrowell Maybe it's like this? Let's try

[dipesh-rawat]

/sig release