Skip to content

Conversation

@wongchar
Copy link
Contributor

Description

Add documentation for new alpha feature gate: prefer-align-cpus-by-uncorecache

Issue

kubernetes/enhancements#4800
kubernetes/kubernetes#126750

@k8s-ci-robot k8s-ci-robot added this to the 1.32 milestone Oct 14, 2024
@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. area/localization General issues or PRs related to localization area/web-development Issues or PRs related to the kubernetes.io's infrastructure, design, or build processes language/en Issues or PRs related to English language language/fr Issues or PRs related to French language language/hi Issues or PRs related to Hindi language labels Oct 14, 2024
@k8s-ci-robot k8s-ci-robot added the language/ja Issues or PRs related to Japanese language label Oct 14, 2024
@k8s-ci-robot
Copy link
Contributor

Welcome @wongchar!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added language/ko Issues or PRs related to Korean language language/pt Issues or PRs related to Portuguese language language/ru Issues or PRs related to Russian language language/uk Issues or PRs related to Ukrainian language language/zh Issues or PRs related to Chinese language cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Oct 14, 2024
@netlify
Copy link

netlify bot commented Oct 14, 2024

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name Link
🔨 Latest commit ace1c3b
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/67460fbbf7ce880008e53186

@netlify
Copy link

netlify bot commented Oct 14, 2024

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit ace1c3b
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/67460fbbd6c6120008974e30
😎 Deploy Preview https://deploy-preview-48340--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@ajcaldelas ajcaldelas force-pushed the split-uncorecache-awareness branch from ae9f6d5 to 6989bb5 Compare October 14, 2024 17:04
@tengqm
Copy link
Contributor

tengqm commented Oct 15, 2024

This commit should be rebased onto dev-1.32 head, IIUC.

@ajcaldelas ajcaldelas force-pushed the split-uncorecache-awareness branch from 6989bb5 to 35e7e1d Compare October 15, 2024 13:57
@k8s-ci-robot k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 15, 2024
@ffromani
Copy link
Contributor

Hi @sftim ! My understanding is we have time to the doc freeze and Nov 19 was the deadline to have documentation PRs submitted and ready for review (not merged!)

If my understanding is right I'm willing to help to kickoff the aforementioned concepts page.

@sftim
Copy link
Contributor

sftim commented Nov 19, 2024

@ffromani that's right. Help is welcome!

@ffromani
Copy link
Contributor

@ffromani that's right. Help is welcome!

ok! I'm willing to take a stab! (xref: #38121)

@ffromani
Copy link
Contributor

@ffromani that's right. Help is welcome!

ok! I'm willing to take a stab! (xref: #38121)

here: #48797

Copy link
Contributor

@ffromani ffromani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM from sig-node. Technical content looks correct to me.

@chanieljdan
Copy link
Contributor

Technical lgtm provided above

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 22, 2024
@chanieljdan
Copy link
Contributor

@reylejano when you get the chance we just need your final review and approval for this one. Thanks!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we can get #48797 merged and merged into v1.32 docs, then the changes here can go there instead (which is what I recommend doing).

See #48340 (review)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm willing to help with #48797, but @tengqm raised some points about the feasibility in the 1.32 timeframe. I guess we can figure out during the review of #48797 ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something else we can do: merge this as-is, but track some work to do after the release to make the docs more readable.

Adding this extra detail harms the quality and readability of the existing task page, so we should plan that work, but we can accept that harm and not block adding this alpha feature on having it appropriately documented.

Ideally we do block beta graduation on getting the docs redone, though. Beta features should have docs that we think are GA quality (and we ship them to find out).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can and will work on getting #48797 ready anyway (https://kubernetes.slack.com/archives/C0BP8PW9G/p1732284959539839). If we decide to not merge for 1.32 due to the too strict timeline, I'll rebase once the other linked content landed, and once cpumanager content is settled I'll move on to memory manager and others:

  1. cpumanager
  2. memory manager
  3. topology manager
  4. (perhaps) device manager, this component doesn't have policies so it can use some refactoring but probably doesn't belong here.

@sftim
Copy link
Contributor

sftim commented Nov 22, 2024

Waiting for docs LGTM
Tech LGTMs noted

/lgtm cancel

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 22, 2024
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 26, 2024
@wongchar wongchar force-pushed the split-uncorecache-awareness branch from b96af01 to ace1c3b Compare November 26, 2024 18:13
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 26, 2024
@wongchar
Copy link
Contributor Author

Rebased to @ffromani 's PR (#48856). Thanks!

@sftim PTAL when you get a chance.

Copy link
Contributor

@ffromani ffromani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

from sig-node

Comment on lines +192 to +194
: Allocate virtual cores, sometimes called hardware threads, across different physical cores (available since Kubernetes v1.31)
`distribute-cpus-across-numa` (alpha, hidden by default)
: spread CPUs across different NUMA domains, aiming for an even balance between the selected domains (available since Kubernetes v1.23)
: Spread CPUs across different NUMA domains, aiming for an even balance between the selected domains (available since Kubernetes v1.23)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is unrelated fix I asked @wongchar to pull in

Comment on lines +197 to +198
`strict-cpu-reservation` (alpha, hidden by default)
: Prevent all the pods regardless of their Quality of Service class to run on reserved CPUs (available since Kubernetes v1.32)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same, fixing a rebase artifact of my previous #48797

defaultValue: false
fromVersion: "1.32"
---
When `PreferAlignCpusByUncoreCache` is enabled while the CPU Manager Policy is set to `static`, containers within a `Guaranteed` pod will individually be aligned to an uncore cache group at a best-effort policy. This feature can optimize performance for certain cache-sensitive workloads by minimizing the cpu allocation across uncore caches.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed in the last upload after rebase on top of #48797

@katcosgrove
Copy link
Contributor

/lgtm

/assign @chanieljdan

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 26, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 8bbd308be16094fd1c9f8c8c63b695d845fb8d3b

@chanieljdan
Copy link
Contributor

tech and docs lgtm provided

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chanieljdan

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:

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 k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 26, 2024
@k8s-ci-robot k8s-ci-robot merged commit b581326 into kubernetes:dev-1.32 Nov 26, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants