diff --git a/doc/source/_includes/single-physical-core-for-platform-function-in-all-in-one-deployments-bec61d5a13f4.rest b/doc/source/_includes/single-physical-core-for-platform-function-in-all-in-one-deployments-bec61d5a13f4.rest
new file mode 100644
index 000000000..691fc7ab8
--- /dev/null
+++ b/doc/source/_includes/single-physical-core-for-platform-function-in-all-in-one-deployments-bec61d5a13f4.rest
@@ -0,0 +1,2 @@
+.. deploy-begin
+.. deploy-end
\ No newline at end of file
diff --git a/doc/source/node_management/kubernetes/index-node-mgmt-kub-5ff5993b9c60.rst b/doc/source/node_management/kubernetes/index-node-mgmt-kub-5ff5993b9c60.rst
index 08745677f..ed32f029c 100644
--- a/doc/source/node_management/kubernetes/index-node-mgmt-kub-5ff5993b9c60.rst
+++ b/doc/source/node_management/kubernetes/index-node-mgmt-kub-5ff5993b9c60.rst
@@ -98,6 +98,7 @@ Configuring CPU core behaviour
    configuring_cpu_core_assignments/configuring-cpu-core-assignments
    configuring_cpu_core_assignments/changing-the-hyper-threading-status
    host-cpu-mhz-parameters-configuration-d9ccf907ede0
+   single-physical-core-for-platform-function-in-all-in-one-deployments-bec61d5a13f4
 
 ------------------------
 Host memory provisioning
diff --git a/doc/source/node_management/kubernetes/single-physical-core-for-platform-function-in-all-in-one-deployments-bec61d5a13f4.rst b/doc/source/node_management/kubernetes/single-physical-core-for-platform-function-in-all-in-one-deployments-bec61d5a13f4.rst
new file mode 100644
index 000000000..09731124e
--- /dev/null
+++ b/doc/source/node_management/kubernetes/single-physical-core-for-platform-function-in-all-in-one-deployments-bec61d5a13f4.rst
@@ -0,0 +1,61 @@
+
+.. _single-physical-core-for-platform-function-in-all-in-one-deployments-bec61d5a13f4:
+
+====================================================================
+Single Physical Core for Platform Function in All-In-One Deployments
+====================================================================
+
+The platform core usage was optimized to operate on a single physical core with
+two logical cores in Hyper-Threading enabled for All-In-One deployments.
+
+During a fresh install of All-In-One systems (non-system-controller) the system
+will be configured to operate with a single physical core for the platform
+function when Hyper-Threading CPU functionality is enabled. In case of
+Hyper-Threading is disabled the system will keep current behavior allocating
+two physical cores for platform function.
+
+The use of single physical core for platform function is only suitable for
+Intel® 4th Generation Xeon® Scalable Processors or above and should not be
+configured for previous Intel® Xeon® CPU families. For All-In-One systems with
+older generation processors, two physical cores (or more) must be configured.
+
+The System does not automatically configures the number of physical cores based
+on the CPU type, the user should perform this configuration. The default is
+Single Core when HT is enabled.
+
+System recommendations and limitations will be available through the |org|
+System Engineering Guidelines.
+
+.. note::
+
+    During an upgrade process, the CPU platform configuration will be retained.
+
+The number of cores allocated to the platform function can be changed through
+the system API and thru deployment manager.
+
+System API:
+
+#.  Lock hosts
+
+.. code-block:: none
+
+    system host-lock <host>
+
+#.  Set cores reserved to platform
+
+.. code-block:: none
+
+    system host-cpu-modify -f platform -p<processor#> <#-of-physical-cores> <host>
+
+#.  Unlock host
+
+.. code-block:: none
+
+    system host-unlock <host>
+
+.. only:: partner
+
+    .. include:: /_includes/single-physical-core-for-platform-function-in-all-in-one-deployments-bec61d5a13f4.rest
+    :start-after: deploy-begin
+    :end-before: deploy-end
+