You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
:description: Describes how to install the Splunk Distribution of OpenTelemetry Collector for Kubernetes with YAML manifests.
10
+
11
+
You can also install the Splunk Distribution of the OpenTelemetry Collector for Kubernetes using resource YAML manifests.
12
+
13
+
.. note:: See also :ref:`otel-install-k8s`.
14
+
15
+
Prerequisites
16
+
==================================
17
+
18
+
To specify the configuration, you need to know your Splunk realm and base64-encoded access token.
19
+
20
+
A configuration file can contain multiple resource manifests. Each manifest applies a specific state to a Kubernetes object. You must configure your manifests for Splunk Observability Cloud only and come with all telemetry types activated for the agent, which is the default if you install using the Helm chart.
21
+
22
+
Determine which manifest you want to use
23
+
===============================================
24
+
25
+
Download the necessary manifest files from :new-page:`the examples repository <https://github.com/signalfx/splunk-otel-collector-chart/tree/main/examples>`. Refer to the ``README`` files for more details on each example.
26
+
27
+
Determine which :ref:`otel-deployment-mode` you want to use, agent or gateway. By default, host monitoring (agent) mode is configured to send data directly to Splunk SaaS endpoints. Host monitoring (agent) mode can be reconfigured to send to a gateway.
28
+
29
+
Update the manifest
30
+
==================================
31
+
32
+
Once you've decided which manifest suits you better, make the following updates:
33
+
34
+
#. In the secret.yaml manifest, update the ``splunk_observability_access_token`` data field with your base64-encoded access token.
35
+
#. Update any configmap-agent.yaml, configmap-gateway.yaml, and configmap-cluster-receiver.yaml manifest files you use. Search for "CHANGEME" to find the values that must be updated to use the rendered manifests directly.
36
+
#. You need to update "CHANGEME" in exporter configurations to the value of the Splunk realm.
37
+
#. You need to update "CHANGEME" in attribute processor configurations to the value of the cluster name.
38
+
39
+
Apply the manifest
40
+
==================================
41
+
42
+
After you've updated them, apply the manifests using ``kubectl``, as shown in the following examples.
43
+
44
+
For host monitoring (agent) mode, download the :new-page:`agent-only manifest directory on GitHub <https://github.com/signalfx/splunk-otel-collector-chart/tree/main/examples/default/rendered_manifests>` for pre-rendered Kubernetes resource manifests that can be applied using the ``kubectl apply`` command after being updated with your token, realm information, and cluster name:
For data forwarding (gateway) mode, download the :new-page:`gateway-only manifest directory on GitHub <https://github.com/signalfx/splunk-otel-collector-chart/tree/main/examples/collector-gateway-only/rendered_manifests>` for pre-rendered Kubernetes resource manifests that can be applied using the ``kubectl apply`` command after being updated with your token, realm information, and cluster name:
0 commit comments