From 382f0a516a62c0e3b15052f0c3d3e8e917549f39 Mon Sep 17 00:00:00 2001
From: Siddhesh Ghadi <sghadi1203@gmail.com>
Date: Fri, 13 Jun 2025 11:05:10 +0530
Subject: [PATCH] Add TLS configuration for custom certificate

Signed-off-by: Siddhesh Ghadi <sghadi1203@gmail.com>
---
 docs/services/webhook.md | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/docs/services/webhook.md b/docs/services/webhook.md
index 4b8ca38a..534ba719 100644
--- a/docs/services/webhook.md
+++ b/docs/services/webhook.md
@@ -74,6 +74,29 @@ metadata:
     notifications.argoproj.io/subscribe.<trigger-name>.<webhook-name>: ""
 ```
 
+4. TLS configuration (optional)
+
+If your webhook server uses a custom TLS certificate, you can configure the notification service to trust it by adding the certificate to the `argocd-tls-certs-cm` ConfigMap as shown below:
+
+```yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: argocd-tls-certs-cm
+data:
+  <hostname>: |
+    -----BEGIN CERTIFICATE-----
+    <TLS DATA>
+    -----END CERTIFICATE-----
+```
+
+*NOTE:*
+*If the custom certificate is not trusted, you may encounter errors such as:*
+```
+Put \"https://...\": x509: certificate signed by unknown authority
+```
+*Adding the server's certificate to `argocd-tls-certs-cm` resolves this issue.*
+
 ## Examples
 
 ### Set GitHub commit status