1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Files
openshift-docs/modules/custom-tuning-example.adoc
Jiri Mencak 9c8e21f1d5 Changes in Node Tuning Operator 4.2 functionality.
- profile settings rollback on profile changes
- the default operator's CR being overwritten
- custom profiles are no longer a Technology Preview
- a complete example of using custom profiles
2019-08-07 16:42:31 +00:00

41 lines
1.0 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 that run an ingress pod with label
`tuned.openshift.io/ingress-pod-label=ingress-pod-label-value`.
As an administrator, use the following command to create a custom tuned CR.
.Example
----
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-pod-label
value: "ingress-pod-label-value"
type: pod
priority: 10
profile: openshift-ingress
_EOF_
----