Documentation for Swap memory management

[iholder101]

Description

Add documentation for KEP-2400 NodeSwap GA.

Basically, this PR does 2 things:

1. Creates a new dedicated swap memory management documentation under content/en/docs/concepts/cluster-administration/swap-memory-management.md. This documentation is heavily based on the contents of the latest blog-post about swap memory: https://kubernetes.io/blog/2025/03/25/swap-linux-improvements/. While the content is very similar, there are minor updates.
2. Removes the old very minimal swap documentation that existed under content/en/docs/concepts/architecture/nodes.md.

This documentation should contain everything the user needs to know for swap GA.

Issue

Fixes #51153

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	cbe99fe
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/686fea1255056a0008de18a6
😎 Deploy Preview	https://deploy-preview-51303--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.

[iholder101]

/cc @ajaysundark

[lmktfy]

Thank you for working on this - it's really needed.

Here's quite a lot of feedback.

[lmktfy]

Partial feedback

[ajaysundark]

I looked into it quick, I'll spend more time to continue review on this.

IMHO, the changes could add more structure for better flow. Admins are often in a hurry. The final document should be easy to scan for.
The official guide will benefit with more value with focus on 'configuration', 'monitoring' and 'troubleshooting' guide. Concepts and details need to be captured, but deep-dive shouldn't mix into configuration details. And I'm not sure on the preferences, but promotional or what to expect next details seem out of place on the official guide. I think you covered lots of these details at the blog post already.

[iholder101]

@ajaysundark thanks for the review! Appreciate it.

I believe your comments are addressed now. Can you please take another look?

[iholder101]

Hey @lmktfy @ajaysundark!
Should I have pushed this PR to the dev-1.34 branch? Should I reopen the PR to do so?

[ajaysundark]

I think you probably can still edit the PR to change the destination branch as dev-1.34. Would need to rebase your original branch as well.

[kannon92]

LGTM from node side.

maybe @haircommander would like to take a look also?

[iholder101]

Thanks a lot @haircommander and @kannon92 for your reviews! Much appreciated!
I believe all comments are now addressed 🙏 PTAL

[haircommander]

should there be something that makes it clear this is linux only early on?

[haircommander]

ah you mention it below that's prbaobly fine

[haircommander]

this is an excellent improvement
/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 6242b4d55807a1ca14edc11f1bf45f7b54d699c6

[iholder101]

@natalisucks can you please take another look?

[lmktfy]

/approve

Thanks, @iholder101.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lmktfy

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/docs/OWNERS [lmktfy]

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

[natalisucks]

thanks everyone for your reviews and work! nice addition, @iholder101 🎉