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

Commit acdf97e

Browse files
Corrected the name deamonset and daemonset to DaemonSet based on user feedback.
1 parent a039be5 commit acdf97e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

gdi/opentelemetry/deployment-modes.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -116,10 +116,10 @@ The Collector for Kubernetes has different deployment options. You can configure
116116

117117
The main deployment modes are:
118118

119-
* Default, which includes the ``agent`` deamonset and the ``clusterReceiver`` deployment component.
120-
* All collector modes, which includes ``agent`` deamonset, and the ``clusterReceiver`` and the ``gateway`` components.
119+
* Default, which includes the ``agent`` DaemonSet and the ``clusterReceiver`` deployment component.
120+
* All collector modes, which includes ``agent`` DaemonSet, and the ``clusterReceiver`` and the ``gateway`` components.
121121

122-
By default, the ``agent`` daemonset deploys a pod running the OpenTelemetry Collector agent in each node of your Kubernetes cluster. The agent pods gather data from your applications, services, and other objects running in their respective nodes, then send the data to Splunk Observability Cloud.
122+
By default, the ``agent`` DaemonSet deploys a pod running the OpenTelemetry Collector agent in each node of your Kubernetes cluster. The agent pods gather data from your applications, services, and other objects running in their respective nodes, then send the data to Splunk Observability Cloud.
123123

124124
.. image:: /_images/gdi/k8s-daemonset.png
125125
:width: 40%

0 commit comments

Comments
 (0)