[WIP] [KEP-5882]: feature blog for DeploymentPodReplacementPolicy placeholder PR

[atiratree]

Add feature blog for DeploymentPodReplacementPolicy.

Tracking issue:

• Deployment Pod Replacement Policy enhancements#5882

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	1d6df81
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/698f33ddda33c000089c8c18
😎 Deploy Preview	https://deploy-preview-45268--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.

[natalisucks]

Howdy everyone – chiming in as part of our 1.30 Release Comms Team 👋 Given the KEP this blog would be about has now been removed from the 1.30 milestone, and the KEP's owner has updated folks per this comment, I wanted @sftim and @nate-double-u to know that this blog won't be included as a feature blog for this release.

@atiratree I'd recommend we close this PR so that there's no confusion about upcoming work, and that you generally have less on your plate for this release and the next one! cc. @kcmartin, our 1.30 Release Comms lead, so everyone is in the loop.

[atiratree]

Hi, yes I am closing this. This feature didn't make it to 1.30.

[atiratree]

reopening for 1.31

[sftim]

/hold

pending assignment of publication date (by release comms)

we'll also keep this held until the v1.31 release has happened

[mbianchidev]

Hey @atiratree , it's Matteo from the 1.31 Release comms team.
I'm reaching out with a reminder that the blog ready for review deadline is July 26, 2024.

Please let me know how we can help with content, review or anything else 😄

[mbianchidev]

Currently waiting for an exception approval on the code PR.

If that happens I'll work closely with @atiratree to understand if this blog is going to make it for this Friday's deadline (26 July) or if an extension of the blog content deadline is needed.
In case this blog would be published, it would be around the 22nd of August, at the tail of the publication schedule.

Another possibility is that creating this blog is not possible, for deadline reasons or if the code exception is not accepted and the KEP status becomes "removed from Milestone".
In this case, I will proceed to change the blog status to "Canceled" and I will ask to @atiratree to close the blog PR.

Let me know if you need anything from the Comms team and keep me posted! (on Slack it would be extra nice)

[mbianchidev]

Hey @atiratree unfortunately the KEP exception has been rejected by the release team, so you should close this blog PR.
I will also proceed to update the blog status to "Canceled" in the comms board.

Thanks for your understanding and cooperation.

[atiratree]

closing per above

[atiratree]

reopening for 1.32

[atiratree]

Unfortunately we did not manage to finish the API review, so this feature is postponed to 1.33

[mbianchidev]

Thanks for letting us know @atiratree !

[dipesh-rawat]

Hi @atiratree @carlory 👋 v1.34 Communications team here,

@carlory as author of #51560, I'd like you to be a writing buddy for @atiratree on this PR.

Please:

• Review this PR, paying attention to the guidelines and review hints
• Update your own PR based on any best practices you identify that should be applied
• Remember to be compassionate with your fellow article author

[dipesh-rawat]

@atiratree When you get a chance, could you please rebase your branch with latest main? We've merged the fix that resolves the Netlify errors, so this should trigger a successful Netlify preview for this PR. Included the steps below to help with the process:

1. Synchronize your fork with upstream
2. Get the new changes on main: git fetch && git checkout main && git pull origin main
3. Rebase your branch on main git checkout <name of your branch> && git rebase -i main

[aibarbetta]

/sig release

[dipesh-rawat]

Hi 👋, v1.34 Communications Team here again!

Since the KEP didn’t meet the code freeze deadline and has been removed from the v1.34 milestone (based on kubernetes/enhancements#3973 (comment)), this KEP won’t be part of the upcoming release.

@atiratree, to keep things clear and streamlined, I recommend closing this PR for now. We’d definitely encourage revisiting it in a future cycle when the KEP is back on track.

Looping in @aibarbetta (v1.34 Comms lead) to keep the team aligned. Thanks so much!

[divya-mohan0209]

Hi @atiratree , SIG Docs will be closing this PR since this will not be worked on as part of the current cycle. Please consider reopening it when you're ready to resume work on the change.

/close

[k8s-ci-robot]

@divya-mohan0209: Closed this PR.

Details

In response to this:

Hi @atiratree , SIG Docs will be closing this PR since this will not be worked on as part of the current cycle. Please consider reopening it when you're ready to resume work on the change.

/close

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.

[atiratree]

/reopen

[k8s-ci-robot]

@atiratree: Reopened this PR.

Details

In response to this:

/reopen

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.

[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

[atiratree]

reopening for 1.35

[atiratree]

DeploymentReplicaSetTerminatingReplicas was promoted to beta, but we need to wait for the DeploymentPodReplacementPolicy to publish the blog. Postponing to 1.36.

[atiratree]

reopening for 1.36

[lmktfy]

Let's close this. @atiratree, please open a brand new PR that includes approximately the same changes.

We have made a number of changes since this was opened and, because it is our oldest open PR (at the time of writing), it is likely to get lost. Opening a new PR will make the work more visible.

/close

[k8s-ci-robot]

@lmktfy: Closed this PR.

Details

In response to this:

Let's close this. @atiratree, please open a brand new PR that includes approximately the same changes.

We have made a number of changes since this was opened and, because it is our oldest open PR (at the time of writing), it is likely to get lost. Opening a new PR will make the work more visible.

/close

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.

[atiratree]

Ok, done: #54621