Skip to content

Commit 80857cd

Browse files
Update doc-Service-Telemetry-Framework/modules/proc_preparing-your-openshift-environment-for-stf.adoc
removed modal verb
1 parent fb2aeaf commit 80857cd

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

doc-Service-Telemetry-Framework/modules/proc_preparing-your-openshift-environment-for-stf.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ The amount of resources that you require to run {ProjectShort} depends on your e
7171

7272
{ProjectShort} uses ElasticSearch to store events, which requires a larger than normal `vm.max_map_count`. The `vm.max_map_count` value is set by default in {OpenShift}.
7373

74-
TIP: If your host platform is a typical {OpenShift} 4 environment, it should not be necessary to make any adjustments. The default node tuning operator is configured to account for ElasticSearch workloads.
74+
TIP: If your host platform is a typical {OpenShift} 4 environment, do not make any adjustments. The default node tuning operator is configured to account for ElasticSearch workloads.
7575

7676
If you want to edit the value of `vm.max_map_count`, you cannot apply node tuning manually using the `sysctl` command because {OpenShift} manages nodes directly. To configure values and apply them to the infrastructure, you must use the node tuning operator. For more information, see https://docs.openshift.com/container-platform/{SupportedOpenShiftVersion}/scalability_and_performance/using-node-tuning-operator.html[Using the Node Tuning Operator].
7777

0 commit comments

Comments
 (0)