From 68d8aa583dbe980d6a25e17e5244a2b3ff6eeb85 Mon Sep 17 00:00:00 2001
From: andrea-mosk <39099407+andrea-mosk@users.noreply.github.com>
Date: Mon, 21 Oct 2024 23:45:56 +0200
Subject: [PATCH] Add server-side apply mention on Argo CD monitoring (#25832)

Co-authored-by: buraizu <bryce.eadie@datadoghq.com>
---
 content/en/continuous_delivery/deployments/argocd.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/en/continuous_delivery/deployments/argocd.md b/content/en/continuous_delivery/deployments/argocd.md
index c9fe7b4e84cfc..522fa7dce2ac1 100644
--- a/content/en/continuous_delivery/deployments/argocd.md
+++ b/content/en/continuous_delivery/deployments/argocd.md
@@ -149,6 +149,10 @@ metadata:
 
 If your Argo CD application deploys more than one service, Datadog can automatically infer the services deployed from an application sync. Datadog infers the services based on the Kubernetes resources that were modified.
 
+<div class="alert alert-warning">
+Automatic service discovery is not supported when <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#server-side-apply">Server-Side Apply</a> is used.
+</div>
+
 To enable automatic service tagging, you need to [monitor your Kubernetes infrastructure using the Datadog Agent][15] and your Kubernetes resources should have the following labels:
 - `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 [Service Catalog][13] based on the service label.