diff --git a/_topic_maps/_topic_map_ms.yml b/_topic_maps/_topic_map_ms.yml
index 6fecd3b821..e6953858e9 100644
--- a/_topic_maps/_topic_map_ms.yml
+++ b/_topic_maps/_topic_map_ms.yml
@@ -390,6 +390,8 @@ Topics:
   File: microshift-greenboot-checking-status
 - Name: Configuring audit logging policies
   File: microshift-audit-logs-config
+- Name: Workload partitioning
+  File: microshift-workload-partitioning
 ---
 Name: Networking
 Dir: microshift_networking
diff --git a/microshift_configuring/microshift-workload-partitioning.adoc b/microshift_configuring/microshift-workload-partitioning.adoc
new file mode 100644
index 0000000000..2967438665
--- /dev/null
+++ b/microshift_configuring/microshift-workload-partitioning.adoc
@@ -0,0 +1,13 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="microshift-workload-partitioning"]
+= Workload partitioning
+include::_attributes/attributes-microshift.adoc[]
+:context: microshift-workload-partitioning
+
+toc::[]
+
+Workload partitioning divides the node CPU resources into distinct CPU sets. The primary objective is to limit the amount of CPU usage for all control plane components which reserves rest of the device CPU resources for workloads of the user.
+
+Workload partitioning allocates reserved set of CPUs to {microshift-short} services, cluster management workloads, and infrastructure pods, ensuring that the remaining CPUs in the cluster deployment are untouched and available exclusively for non-platform workloads.
+
+include::modules/microshift-enabling-workload-partitioning.adoc[leveloffset=+1]
\ No newline at end of file
diff --git a/modules/microshift-enabling-workload-partitioning.adoc b/modules/microshift-enabling-workload-partitioning.adoc
new file mode 100644
index 0000000000..f038b7ef6d
--- /dev/null
+++ b/modules/microshift-enabling-workload-partitioning.adoc
@@ -0,0 +1,106 @@
+// Module included in the following assemblies:
+//
+// * microshift_configuring/microshift-workload-partitioning.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="microshift-enabling-workload-partitioning_{context}"]
+= Enabling workload partitioning
+
+To enable workload partitioning on {microshift-short}, make the following configuration changes:
+
+* Update the {microshift-short} `config.yaml` file to include the kubelet configuration file.
+* Create the CRI-O systemd and configuration files.
+* Create and update the systemd configuration file for the {microshift-short} and CRI-O services respectively.
+
+.Procedure
+
+. Update the {microshift-short} `config.yaml` file to include the kubelet configuration file to enable and configure CPU Manager for the workloads:
+* Create the kubelet configuration file in the path `/etc/kubernetes/openshift-workload-pinning`. The kubelet configuration directs the kubelet to modify the node resources based on the capacity and allocatable CPUs.
++
+.kubelet configuration example
+[source,yaml]
+----
+# ...
+{
+  "management": {
+    "cpuset": "0,6,7" <1>
+  }
+}
+# ...
+----
+<1> The `cpuset` applies to a machine with 8 VCPUs (4 cores) and is valid throughout the document.
+* Update the {microshift-short} config.yaml file in the path `/etc/microshift/config.yaml`. Embed the kubelet configuration in the {microshift-short} `config.yaml` file to enable and configure CPU Manager for the workloads.
++
+.{microshift-short} `config.yaml` example
+[source,yaml]
+----
+# ...
+kubelet:
+  reservedSystemCPUs: 0,6,7 <1>
+  cpuManagerPolicy: static
+  cpuManagerPolicyOptions:
+    full-pcpus-only: "true" <2>
+  cpuManagerReconcilePeriod: 5s
+# ...
+----
+<1> Exclusive cpuset for the system daemons and the interrupts/timers.
+<2> kubelet configuration sets the `CPUManagerPolicyOptions` option to `full-pcpus-only` to ensure allocation of whole cores to the containers workload.
+
+. Create the CRI-O systemd and configuration files:
+* Create the CRI-O configuration file in the path `/etc/crio/crio.conf.d/20-microshift-workload-partition.conf` which overrides the default configuration that already exists in the `11-microshift-ovn.conf` file.
++
+.CRI-O configuration example
+[source,yaml]
+----
+# ...
+[crio.runtime]
+infra_ctr_cpuset = "0,6,7"
+
+[crio.runtime.workloads.management]
+activation_annotation = "target.workload.openshift.io/management"
+annotation_prefix = "resources.workload.openshift.io"
+resources = { "cpushares" = 0, "cpuset" = "0,6,7" }
+# ...
+----
+* Create the systemd file for CRI-O in the path `/etc/systemd/system/crio.service.d/microshift-cpuaffinity.conf`.
++
+.CRI-O systemd configuration example
+[source,yaml]
+----
+# ...
+[Service]
+CPUAffinity=0,6,7
+# ...
+----
+
+. Create and update the systemd configuration file with `CPUAffinity` value for the {microshift-short} and CRI-O services:
+* Create the {microshift-short} services systemd file in the path `/etc/systemd/system/microshift.service.d/microshift-cpuaffinity.conf`. {microshift-short} will be pinned using the systemd `CPUAffinity` value.
++
+.{microshift-short} services systemd configuration example
+[source,yaml]
+----
+# ...
+[Service]
+CPUAffinity=0,6,7
+# ...
+----
+* Update the `CPUAffinity` value in the {microshift-short} ovs-vswitchd systemd file in the path `/etc/systemd/system/ovs-vswitchd.service.d/microshift-cpuaffinity.conf`.
++
+.{microshift-short} ovs-vswitchd systemd configuration example
+[source,yaml]
+----
+# ...
+[Service]
+CPUAffinity=0,6,7
+# ...
+----
+* Update the `CPUAffinity` value in the {microshift-short} ovsdb-server systemd file in the path `/etc/systemd/system/ovsdb-server.service.d/microshift-cpuaffinity.conf`
++
+.{microshift-short} ovsdb-server systemd configuration example
+[source,yaml]
+----
+# ...
+[Service]
+CPUAffinity=0,6,7
+# ...
+----
\ No newline at end of file