Skip to content

Commit

Permalink
Add Annotations v2 for control plane configuration (#19344)
Browse files Browse the repository at this point in the history
  • Loading branch information
drichards-87 authored Jan 9, 2025
1 parent 27bba67 commit dea8e5e
Showing 1 changed file with 23 additions and 0 deletions.
23 changes: 23 additions & 0 deletions istio/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,9 @@ Customize this file with any additional configurations. See the [sample istio.d/
##### Control plane configuration
To monitor the Istio control plane and report the `mixer`, `galley`, `pilot`, and `citadel` metrics, you must configure the Agent to monitor the `istiod` deployment. In Istio v1.5 or later, apply the following pod annotations for the deployment `istiod` in the `istio-system` namespace:

<!-- xxx tabs xxx -->
<!-- xxx tab "Annotations v1" xxx -->

```yaml
ad.datadoghq.com/discovery.checks: |
{
Expand All @@ -79,6 +82,26 @@ ad.datadoghq.com/discovery.checks: |
}
```

<!-- xxz tab xxx -->
<!-- xxx tab "Annotations v2" xxx -->

**Note**: Annotations v2 is supported for Agent v7.36+.

```yaml
ad.datadoghq.com/<CONTAINER_IDENTIFIER>.checks: |
{
"Istio": {
"istiod_endpoint": "http://%%host%%:15014/metrics",
"use_openmetrics": "true"
}
}
```

<!-- xxz tab xxx -->
<!-- xxz tabs xxx -->



This annotation specifies the container `discovery` to match the default container name of the Istio container in this pod. Replace this annotation `ad.datadoghq.com/<CONTAINER_NAME>.checks` with the name (`.spec.containers[i].name`) of your Istio container if yours differs.

The method for applying these annotations varies depending on the [Istio deployment strategy (Istioctl, Helm, Operator)][22] used. Consult the Istio documentation for the proper method to apply these pod annotations. See the [sample istio.d/conf.yaml][8] for all available configuration options.
Expand Down

0 comments on commit dea8e5e

Please sign in to comment.