Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit c4d35e9

Browse files
Merge pull request #2033 from splunk/urbiz-OD6291-helm-images
[6291]: Helm images
2 parents 73445f6 + ac7e4b4 commit c4d35e9

File tree

5 files changed

+319
-191
lines changed

5 files changed

+319
-191
lines changed

gdi/opentelemetry/collector-kubernetes/collector-kubernetes-intro.rst

Lines changed: 49 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,10 @@ Get started with the Collector for Kubernetes
1111
:maxdepth: 5
1212
:hidden:
1313

14-
Install the Collector for Kubernetes <install-k8s.rst>
14+
Install with Helm <install-k8s.rst>
15+
Helm components <kubernetes-helm-architecture>
16+
Helm releases and images <kubernetes-helm-releases>
17+
Install with YAML manifests <install-k8s-manifests.rst>
1518
Kubernetes (EKS Add-on) <install-k8s-addon-eks.rst>
1619
Configure with Helm <kubernetes-config.rst>
1720
Advanced config <kubernetes-config-advanced.rst>
@@ -22,28 +25,65 @@ Get started with the Collector for Kubernetes
2225
Troubleshoot <troubleshoot-k8s.rst>
2326
Troubleshoot containers <troubleshoot-k8s-container.rst>
2427
Support <kubernetes-support.rst>
25-
k8s-infrastructure-tutorial/about-k8s-tutorial
26-
collector-configuration-tutorial-k8s/about-collector-config-tutorial.rst
28+
Tutorial: Monitor your Kubernetes environment <k8s-infrastructure-tutorial/about-k8s-tutorial.rst>
29+
Tutorial: Configure the Collector for Kubernetes <collector-configuration-tutorial-k8s/about-collector-config-tutorial.rst>
2730

28-
To install and configure the Splunk Distribution of the OpenTelemetry Collector for Kubernetes, follow these docs:
31+
To install, configure and use the Splunk Distribution of the Collector for Kubernetes follow this documentation.
32+
33+
.. raw:: html
34+
35+
<embed>
36+
<h2>Install the Collector for Kubernetes<a name="k8s-install" class="headerlink" href="#k8s-install" title="Permalink to this headline">¶</a></h2>
37+
</embed>
38+
39+
To install the Splunk Distribution of the OpenTelemetry Collector for Kubernetes using the Helm chart, read and follow these docs:
2940

3041
* :ref:`otel-install-k8s`
31-
* :ref:`install-k8s-addon-eks`
32-
* :ref:`otel-kubernetes-config`
33-
* By default, you'll obtain these :ref:`Kubernetes metrics <ootb-metrics-k8s>`
42+
* :ref:`kubernetes-helm-architecture`
43+
* :ref:`kubernetes-helm-releases`
44+
45+
Optionally, you can also:
46+
47+
* :ref:`otel-install-k8s-manifests`
48+
* :ref:`Deploy the Collector as an AWS EKS Add-on <install-k8s-addon-eks>`
49+
50+
.. note:: By default, you'll obtain these :ref:`Kubernetes metrics <ootb-metrics-k8s>`.
51+
52+
.. raw:: html
3453

35-
For advanced configuration options, see:
54+
<embed>
55+
<h2>Configure the Collector for Kubernetes<a name="k8s-configure" class="headerlink" href="#k8s-configure" title="Permalink to this headline">¶</a></h2>
56+
</embed>
3657

58+
To configure the Collector, see:
59+
60+
* :ref:`otel-kubernetes-config`
3761
* :ref:`otel-kubernetes-config-advanced`
3862
* :ref:`kubernetes-config-logs`
3963
* :ref:`discovery-mode-k8s`
4064

65+
.. raw:: html
66+
67+
<embed>
68+
<h2>Upgrade, uninstall and troubleshoot<a name="k8s-ts" class="headerlink" href="#k8s-ts" title="Permalink to this headline">¶</a></h2>
69+
</embed>
70+
4171
To upgrade or uninstall, see:
4272

4373
* :ref:`otel-kubernetes-upgrade`
4474
* :ref:`otel-kubernetes-uninstall`
4575

46-
.. note:: If you have any installation or configuration issues, refer to :ref:`otel-troubleshooting` and :ref:`troubleshoot-k8s`.
76+
If you have any installation or configuration issues, refer to:
77+
78+
* :ref:`otel-troubleshooting`
79+
* :ref:`troubleshoot-k8s`
80+
* :ref:`kubernetes-support`
81+
82+
.. raw:: html
83+
84+
<embed>
85+
<h2>Tutorials<a name="k8s-tutorials" class="headerlink" href="#k8s-tutorials" title="Permalink to this headline">¶</a></h2>
86+
</embed>
4787

4888
For a walkthrough of common tasks related to the OpenTelemetry Collector for Kubernetes, see:
4989

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
.. _otel-install-k8s-manifests:
2+
.. _resource-yaml-manifests:
3+
4+
********************************************************************
5+
Install the Collector for Kubernetes with YAML manifests
6+
********************************************************************
7+
8+
.. meta::
9+
: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:
45+
46+
.. code-block:: bash
47+
48+
kubectl apply -f <agent-manifest-directory> --recursive
49+
50+
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:
51+
52+
.. code-block:: bash
53+
54+
kubectl apply -f <gateway-manifest-directory> --recursive
55+
56+
Use templates
57+
==================================
58+
59+
You can create your own manifest YAML files with customized parameters using ``helm template`` command.
60+
61+
.. code-block:: bash
62+
63+
helm template --namespace default --set cloudProvider='aws' --set distribution='openshift' --set splunkObservability.accessToken='KUwtoXXXXXXXX' --set clusterName='my-openshift-EKS-dev-cluster' --set splunkObservability.realm='us1' --set gateway.enabled='false' --output-dir <rendered_manifests_dir> --generate-name splunk-otel-collector-chart/splunk-otel-collector
64+
65+
If you prefer, you can update the values.yaml file first.
66+
67+
.. code-block:: bash
68+
69+
helm template --namespace default --values values.yaml --output-dir <rendered_manifests_dir> --generate-name splunk-otel-collector-chart/splunk-otel-collector
70+
71+
Manifest files will be created in your specified folder ``<rendered_manifests_dir>``.
72+
73+
Manifest examples
74+
==================================
75+
See the following manifest to set security constraints:
76+
77+
.. github:: yaml
78+
:url: https://raw.githubusercontent.com/signalfx/splunk-otel-collector-chart/main/examples/distribution-openshift/rendered_manifests/securityContextConstraints.yaml
79+
80+
Next steps
81+
==================================
82+
83+
After installing the Collector you can:
84+
85+
* :ref:`otel-kubernetes-config`
86+
* :ref:`otel-kubernetes-config-advanced`
87+
* :ref:`otel-kubernetes-config-logs`
88+
* :ref:`troubleshoot-k8s`
89+
* :ref:`apm`

0 commit comments

Comments
 (0)