Skip to content

Commit ed52d66

Browse files
authored
Merge pull request #43353 from jmencak/4.11-nto-cloud-provider
NTO: Cloud provider specific TuneD profiles
2 parents f8a0941 + c73f5f2 commit ed52d66

File tree

1 file changed

+44
-0
lines changed

1 file changed

+44
-0
lines changed

modules/custom-tuning-specification.adoc

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -181,3 +181,47 @@ To minimize node reboots, label the target nodes with a label the machine config
181181
// matchLabels:
182182
// node-role.kubernetes.io/worker-custom: ""
183183
// EOF
184+
185+
*Cloud provider-specific TuneD profiles*
186+
187+
With this functionality, all Cloud provider-specific nodes can conveniently
188+
be assigned a TuneD profile specifically tailored to a given Cloud provider
189+
on a {product-title} cluster. This can be accomplished without adding
190+
additional node labels or grouping nodes into machine config pools.
191+
192+
This functionality takes advantage of `spec.providerID` node object values
193+
in the form of `<cloud-provider>://<cloud-provider-specific-id>` and writes
194+
the file `/var/lib/tuned/provider` with the value `<cloud-provider>` in NTO
195+
operand containers. The content of this file is then used by TuneD to load
196+
`provider-<cloud-provider>` profile if such profile exists.
197+
198+
The `openshift` profile that both `openshift-control-plane` and
199+
`openshift-node` profiles inherit settings from is now updated to use
200+
this functionality through the use of conditional profile loading.
201+
Neither NTO nor TuneD currently ship any Cloud provider-specific profiles.
202+
However, it is possible to create a custom profile `provider-<cloud-provider>`
203+
that will be applied to all Cloud provider-specific cluster nodes.
204+
205+
.Example GCE Cloud provider profile
206+
[source,yaml]
207+
----
208+
apiVersion: tuned.openshift.io/v1
209+
kind: Tuned
210+
metadata:
211+
name: provider-gce
212+
namespace: openshift-cluster-node-tuning-operator
213+
spec:
214+
profile:
215+
- data: |
216+
[main]
217+
summary=GCE Cloud provider-specific profile
218+
# Your tuning for GCE Cloud provider goes here.
219+
name: provider-gce
220+
----
221+
222+
[NOTE]
223+
====
224+
Due to profile inheritance, any setting specified in the
225+
`provider-<cloud-provider>` profile will be overwritten by the `openshift`
226+
profile and its child profiles.
227+
====

0 commit comments

Comments
 (0)