KEP-5495: blog post about IPVS deprecation#56422
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@victord-ef, would you be willing to be a writing buddy on this? @danwinship, I hope you'd be willing to buddy up with @victord-ef who is planning to write a follow up for #56091. How does that sound? |
|
Bear in mind @victord-ef that right now this is a draft. You absolutely can provide help and early feedback, and that is what the buddying process is about. However, what you see in this PR is explicitly not marked as ready for review yet. Anyway, I hope you can both help each other progress the two articles. |
| layout: blog | ||
| title: "Deprecation of kube-proxy IPVS backend" | ||
| date: 2026-xx-xx | ||
| slug: ipvs-kube-proxy-deprecation |
There was a problem hiding this comment.
The slug and filename should match
consider changing the filename or vice versa
The path may look like content/en/blog/_posts/2026/ipvs-kube-proxy-deprecation.md
| --- | ||
| layout: blog | ||
| title: "Deprecation of kube-proxy IPVS backend" | ||
| date: 2026-xx-xx |
There was a problem hiding this comment.
| date: 2026-xx-xx | |
| draft: true |
There was a problem hiding this comment.
note that the comment left on the KEP issue says:
In your placeholder PR, use XX characters for the blog date in the front matter and file name.
|
Absolutely, I’d appreciate being your writing buddy! |
|
@lmktfy sure |
Description
Blog post about IPVS deprecation, and migrating to iptables or nftables
Issue
KEP: kubernetes/enhancements#5495