Ensure to add v1.33 prefix for title

[rytswd]

This seems to be the convention we used to use for the previous cycles. I will document in the handbook about how the future Feature Blogs should be created with correct front matter to begin with (including draft: true)

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	9ec1aea
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/680edfe250488200080cfccd
😎 Deploy Preview	https://deploy-preview-50666--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.

[rytswd]

Looking at other blogs, I see most of the old blogs have the slug with kubernetes-1-XX form, except for the mid cycle and release announcement, which have kubernetes-v1-XX. To keep it consistent throughout, it may be better to always use "v" prefix everywhere? (Although this wouldn't be the case for old blogs, it would be simpler to explain for future blogs)

CC @natalisucks @lmktfy

[rytswd]

/sig release

[natalisucks]

/lgtm

[lmktfy]

/hold

/lgtm cancel

[lmktfy]

We don't change blog article slugs after publication. That can make for a poor UX.

[lmktfy]

We don't change blog article slugs after publication. That can make for a poor UX.

[lmktfy]

@rytswd it's OK to change article titles after publication (we still try to avoid it), but we almost never change:

• article publication date / time
• article slug

This is because if we do that, it can make the changed article appear new to people using feed readers, and we have a lot of people we try not to annoy if we did do that.

[rytswd]

@lmktfy That's fair, and I will be affected by that myself 🫠 Although I personally wouldn't mind if the changes are only for few articles, I can understand this can be annoying. I will not update the old slugs to keep them untouched.

However, I do think the title should be updated for consistency. Because this shouldn't affect those external readers, and this would affect only few at this point, I'd like to still push for the title prefix update. It's better UX when all the Feature Blogs are clearly aligned from the blog title IMO.

(This should have been caught earlier, and I will be making sure to update the handbook accordingly.)

[natalisucks]

@lmktfy do we have the rules you've noted about not changing article slugs and blog publication date/times in our style guide or blog review guidelines? i've had a quick review now to check and may have missed it, thanks in advance.

[reylejano]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: reylejano

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 [reylejano]

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

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: d2e05bc90db3078f44d0187aab006ece346528ae

[lmktfy]

OK to change it
/hold cancel