initial commit

Author: mbechtold-splunk

gdi/opentelemetry/collector-kubernetes/kubernetes-config-advanced.rst

@@ -503,3 +503,37 @@ Cluster Receiver support
 The Cluster receiver is a 1-replica deployment of the OpenTelemetry Collector. Because the Kubernetes control plane can select any available node to run the cluster receiver pod (unless ``clusterReceiver.nodeSelector`` is explicitly set to pin the pod to a specific node), ``hostPath`` or ``local`` volume mounts don't work for such environments.
 
 Data persistence is currently not applicable to the Kubernetes cluster metrics and Kubernetes events.
+
+Configure special Kubernetes distributions
+================================================
+
+To collect telemetry data from specific Kubernetes distributions such as RedHat OpenShift, EKS, and GCP, you might have to create additional configurations. 
+
+Monitor OpenShift infrastructure nodes
+------------------------------------------------
+
+By default, the Splunk Distribution of OpenTelemetry Collector for Kubernetes doesn't collect data from OpenShift infrastructure nodes. 
+
+You can customize the Collector Helm Chart file to activate data collection from OpenShift infrastructure nodes. To do so, complete the following steps:
+
+#. Open your values.yaml file for the Helm Chart.
+#. Copy and paste the following YAML snippet into the values.yaml file:
+
+    .. code-block:: yaml
+
+      tolerations:
+        - key: node-role.kubernetes.io/master
+          effect: NoSchedule
+        - key: node-role.kubernetes.io/control-plane
+          effect: NoSchedule
+        - key: node-role.kubernetes.io/infra
+          effect: NoSchedule
+          operator: Exists
+
+#. Install the Collector using the Helm Chart:
+
+    .. code-block:: bash
+
+      helm install my-splunk-otel-collector --values values.yaml splunk-otel-collector-chart/splunk-otel-collector
+
+.. note:: Monitoring OpenShift infrastructure nodes might pose a security risk depending on which method you used to create the Kubernetes environment.