Skip to content

Add rollouts docs | SDCD-1289 #29537

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 4 commits into from
May 28, 2025
Merged

Add rollouts docs | SDCD-1289 #29537

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4b06f22
Add rollouts docs
Aaron-9900 May 26, 2025
cae7f9f
Fix tabs
Aaron-9900 May 26, 2025
680754d
Undo random changes
Aaron-9900 May 27, 2025
9288551
Apply suggestions from code review
Aaron-9900 May 28, 2025
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
22 changes: 14 additions & 8 deletions content/en/continuous_delivery/deployments/argocd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,10 +31,15 @@

The setup below uses the [Webhook notification service][5] of Argo CD to send notifications to Datadog.

First, add your [Datadog API Key][11] in the `argocd-notifications-secret` secret with the `dd-api-key` key. See [the Argo CD guide][2] for information on modifying the `argocd-notifications-secret`. For sending notifications, the setup is different depending on whether you installed Argo CD using Helm or the regular setup (using `kubectl apply`).
First, add your [Datadog API Key][11] in the `argocd-notifications-secret` secret with the `dd-api-key` key. See [the Argo CD guide][2] for information on modifying the `argocd-notifications-secret`.

Choose one of the following setup methods based on how you installed Argo CD:

- **Regular setup (kubectl apply)**: For standard Argo CD installations using `kubectl apply`
- **Helm**: For Helm-based Argo CD deployments

### Method 1: Regular setup (kubectl apply)

{{< tabs >}}
{{% tab "Regular setup (with kubectl apply)" %}}
Modify the `argocd-notifications-cm` ConfigMap to create the notification service, template, and trigger to send notifications to Datadog:

```yaml
Expand Down Expand Up @@ -70,8 +75,9 @@
- when: app.status.operationState.phase == 'Running' and app.status.health.status in ['Healthy', 'Degraded']
send: [cd-visibility-template]
```
{{% /tab %}}
{{% tab "Helm" %}}

### Method 2: Helm

If you used Helm to install Argo CD, add the following configuration to your `values.yaml`:

```yaml
Expand Down Expand Up @@ -106,8 +112,8 @@
- when: app.status.operationState.phase == 'Running' and app.status.health.status in ['Healthy', 'Degraded']
send: [cd-visibility-template]
```
{{% /tab %}}
{{< /tabs >}}

### Configuration Summary

Check warning on line 116 in content/en/continuous_delivery/deployments/argocd.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.headings 

'Configuration Summary' should use sentence-style capitalization.

The following resources have been added:
1. The `cd-visibility-webhook` service targets the Datadog intake and configures the correct headers for the request. The `DD-API-KEY` header references the `dd-api-key` entry added previously in the `argocd-notifications-secret`.
Expand Down Expand Up @@ -239,7 +245,7 @@
- `tags.datadoghq.com/service` (required): specifies the Datadog service of this resource. For more information, see [Unified Service Tagging][18].
- `team` (optional): specifies the Datadog team of this resource. If this label is omitted, the team is automatically retrieved from [Software Catalog][13] based on the service label.

Only the Kubernetes resources with the following kinds are eligible: `Deployment`, `ReplicaSet`, `StatefulSet`, `Service`, `DaemonSet`, `Pod`, `Job`, and `CronJob`.
Only the Kubernetes resources with the following kinds are eligible: `Deployment`, `Rollout`, `ReplicaSet`, `StatefulSet`, `Service`, `DaemonSet`, `Pod`, `Job`, and `CronJob`.

Add the following annotations to your Argo CD application:
- `dd_multiservice`: `true`. This annotation specifies whether Datadog automatically infers the services deployed in a sync based on the changed Kubernetes resources.
Expand Down
Loading