1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Files
openshift-docs/modules/custom-tuning-example.adoc
2020-08-07 17:59:01 +00:00

46 lines
1.2 KiB
Plaintext

// Module included in the following assemblies:
//
// * scalability_and_performance/using-node-tuning-operator.adoc
[id="custom-tuning-example_{context}"]
= Custom tuning example
The following CR applies custom node-level tuning for
{product-title} nodes with label
`tuned.openshift.io/ingress-node-label` set to any value.
As an administrator, use the following command to create a custom Tuned CR.
.Custom tuning example
[source,terminal]
----
$ oc create -f- <<_EOF_
apiVersion: tuned.openshift.io/v1
kind: Tuned
metadata:
name: ingress
namespace: openshift-cluster-node-tuning-operator
spec:
profile:
- data: |
[main]
summary=A custom OpenShift ingress profile
include=openshift-control-plane
[sysctl]
net.ipv4.ip_local_port_range="1024 65535"
net.ipv4.tcp_tw_reuse=1
name: openshift-ingress
recommend:
- match:
- label: tuned.openshift.io/ingress-node-label
priority: 10
profile: openshift-ingress
_EOF_
----
[IMPORTANT]
====
Custom profile writers are strongly encouraged to include the default Tuned
daemon profiles shipped within the default Tuned CR. The example above uses the
default `openshift-control-plane` profile to accomplish this.
====