kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #48339 from PiotrProkop/stable-topology-manager-policies 

topology-manager: promoto TopologyManagerPolicyOptions to stable
pull/48498/head
Kubernetes Prow Robot 2024-11-04 00:31:27 +00:00 committed by GitHub
parent 3ab5d0d410 013fa96f41
commit 6236c20b58
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/en/docs/reference/command-line-tools-reference/feature-gates/topology-manager-policy-options.md
View File

@ -6,13 +6,17 @@ _build:
render: false render: false
stages: stages:
- stage: alpha - stage: alpha
defaultValue: false defaultValue: false
fromVersion: "1.26" fromVersion: "1.26"
toVersion: "1.27" toVersion: "1.27"
- stage: beta - stage: beta
defaultValue: true defaultValue: true
fromVersion: "1.28" fromVersion: "1.28"
toVersion: "1.31"
- stage: stable
defaultValue: true
fromVersion: "1.32"
--- ---
Enable [fine-tuning](/docs/tasks/administer-cluster/topology-manager/#topology-manager-policy-options) Enable [fine-tuning](/docs/tasks/administer-cluster/topology-manager/#topology-manager-policy-options)
of topology manager policies. of topology manager policies.

9
content/en/docs/tasks/administer-cluster/topology-manager.md
View File

@ -223,12 +223,11 @@ You can toggle groups of options on and off based upon their maturity level usin
You will still have to enable each option using the `TopologyManagerPolicyOptions` kubelet option. You will still have to enable each option using the `TopologyManagerPolicyOptions` kubelet option.
### `prefer-closest-numa-nodes` (beta) {#policy-option-prefer-closest-numa-nodes} ### `prefer-closest-numa-nodes` {#policy-option-prefer-closest-numa-nodes}
The `prefer-closest-numa-nodes` option is beta since Kubernetes 1.28. In Kubernetes {{< skew currentVersion >}} The `prefer-closest-numa-nodes` option is GA since Kubernetes 1.32. In Kubernetes {{< skew currentVersion >}}
this policy option is visible by default provided that the `TopologyManagerPolicyOptions` and this policy option is visible by default provided that the `TopologyManagerPolicyOptions`
`TopologyManagerPolicyBetaOptions` [feature gates](/docs/reference/command-line-tools-reference/feature-gates/) [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled.
are enabled.
The Topology Manager is not aware by default of NUMA distances, and does not take them into account when making The Topology Manager is not aware by default of NUMA distances, and does not take them into account when making
Pod admission decisions. This limitation surfaces in multi-socket, as well as single-socket multi NUMA systems, Pod admission decisions. This limitation surfaces in multi-socket, as well as single-socket multi NUMA systems,