// Module included in the following assemblies:
//
// * scalability_and_performance/using-topology-manager.adoc
// * post_installation_configuration/node-tasks.adoc

:_mod-docs-content-type: PROCEDURE
[id="setting_up_topology_manager_{context}"]
= Setting up Topology Manager

[role="_abstract"]
To use Topology Manager, you must configure an allocation policy in the `KubeletConfig` custom resource (CR) named `cpumanager-enabled`. This file might exist if you have set up CPU Manager. If the file does not exist, you can create the file.

.Prerequisites

* Configure the CPU Manager policy to be `static`.

.Procedure

. To activate Topology Manager, configure the Topology Manager allocation policy in the custom resource.
+
[source,terminal]
----
$ oc edit KubeletConfig cpumanager-enabled
----
+
[source,yaml]
----
apiVersion: machineconfiguration.openshift.io/v1
kind: KubeletConfig
metadata:
  name: cpumanager-enabled
spec:
  machineConfigPoolSelector:
    matchLabels:
      custom-kubelet: cpumanager-enabled
  kubeletConfig:
     cpuManagerPolicy: static
     cpuManagerReconcilePeriod: 5s
     topologyManagerPolicy: single-numa-node
----
+
--
* `cpuManagerPolicy` must be `static` with a lowercase `s`.
* `topologyManagerPolicy` specifies your selected Topology Manager allocation policy. In this example, the policy is `single-numa-node`. Acceptable values are: `default`, `best-effort`, `restricted`, `single-numa-node`.
--
