openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

TELCODOCS-627: updating operator reference to include PA controller

Browse Source
This commit is contained in:
Ronan Hennessy
2022-06-09 11:16:31 +01:00
committed by openshift-cherrypick-robot
parent 2eebffd16e
commit e1c2a3e2eb
2 changed files with 21 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
modules/node-tuning-operator.adoc
View File

@@ -23,13 +23,25 @@ ifdef::operators[]
[discrete]
== Purpose
endif::operators[]
The Node Tuning Operator helps you manage node-level tuning by orchestrating the TuneD daemon. The majority of high-performance applications require some level of kernel tuning. The Node Tuning Operator provides a unified management interface to users of node-level sysctls and more flexibility to add custom tuning specified by user needs.
The Node Tuning Operator helps you manage node-level tuning by orchestrating the TuneD daemon and achieves low latency performance by using the Performance Profile controller. The majority of high-performance applications require some level of kernel tuning. The Node Tuning Operator provides a unified management interface to users of node-level sysctls and more flexibility to add custom tuning specified by user needs.
The Operator manages the containerized TuneD daemon for {product-title} as a Kubernetes daemon set. It ensures the custom tuning specification is passed to all containerized TuneD daemons running in the cluster in the format that the daemons understand. The daemons run on all nodes in the cluster, one per node.
Node-level settings applied by the containerized TuneD daemon are rolled back on an event that triggers a profile change or when the containerized TuneD daemon is terminated gracefully by receiving and handling a termination signal.
The Node Tuning Operator uses the Performance Profile controller to implement automatic tuning to achieve low latency performance for {product-title} applications. The cluster administrator configures a performance profile to define node-level settings such as the following:
* Updating the kernel to kernel-rt.
* Choosing CPUs for housekeeping.
* Choosing CPUs for running workloads.
The Node Tuning Operator is part of a standard {product-title} installation in version 4.1 and later.
[NOTE]
====
In earlier versions of {product-title}, the Performance Addon Operator was used to implement automatic tuning to achieve low latency performance for OpenShift applications. In {product-title} 4.11, these functions are part of the Node Tuning Operator.
====
ifdef::operators[]
[discrete]
== Project

8
operators/operator-reference.adoc
View File

@@ -56,6 +56,14 @@ include::modules/machine-api-operator.adoc[leveloffset=+1]
include::modules/machine-config-operator.adoc[leveloffset=+1]
include::modules/operator-marketplace.adoc[leveloffset=+1]
include::modules/node-tuning-operator.adoc[leveloffset=+1]
[discrete]
[role="_additional-resources"]
[id="platform-operators-ref-nto-addtl-resources"]
=== Additional resources
* xref:../scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.adoc#cnf-understanding-low-latency_cnf-master[Low latency tuning of OCP nodes]
include::modules/openshift-apiserver-operator.adoc[leveloffset=+1]
include::modules/cluster-openshift-controller-manager-operators.adoc[leveloffset=+1]