Skip to content

[OTAGENT-643] Update configs on DDOT Gateway #32657

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 6, 2025
Merged

[OTAGENT-643] Update configs on DDOT Gateway #32657

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions content/en/opentelemetry/setup/ddot_collector/install/kubernetes_gateway.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,12 +51,12 @@ Before you begin, ensure you have the following:
* **Software**:
* A Kubernetes cluster (v1.29+). EKS Fargate and GKE Autopilot are not supported.
* [Helm][3] (v3+).
* Datadog Helm chart version 3.137.1 or higher.
* Datadog Helm chart version 3.143.0 or higher.
* [kubectl][4].

## Installation and configuration

This guide uses the Datadog Helm chart to configure the DDOT Collector gateway.
This guide uses the Datadog Helm chart to configure the DDOT Collector gateway. Check out all the available configurations on the [Datadog Helm chart README][8].

### Deploying the gateway with a daemonset

Expand Down Expand Up @@ -353,21 +353,21 @@ To ensure APM Stats are calculated on 100% of your traces before sampling, the <

### Using a custom Collector image

To use a custom-built Collector image for your gateway, specify the image repository and tag under `agents.image`. This follows the same process as the DaemonSet deployment. For more details, see [Use Custom OpenTelemetry Components][5].
To use a custom-built Collector image for your gateway, specify the image repository and tag under `otelAgentGateway.image`. If you need instructions on how to build the custom images, see [Use Custom OpenTelemetry Components][5].

```yaml
# values.yaml
targetSystem: "linux"
agents:
enabled: false
image:
repository: <YOUR REPO>
tag: <IMAGE TAG>
doNotCheckTag: true
clusterAgent:
enabled: false
otelAgentGateway:
enabled: true
image:
repository: <YOUR REPO>
tag: <IMAGE TAG>
doNotCheckTag: true
ports:
- containerPort: "4317"
name: "otel-grpc"
Expand Down Expand Up @@ -515,3 +515,4 @@ For advanced scenarios, you can deploy multiple gateway layers to create a proce
[5]: /opentelemetry/setup/ddot_collector/custom_components
[6]: https://opentelemetry.io/docs/collector/deployment/gateway/
[7]: https://github.com/open-telemetry/opentelemetry-collector/tree/main/config/configtls
[8]: http://github.com/DataDog/helm-charts/blob/main/charts/datadog/README.md
Loading