From d784c4f32973649c2df81a58dc27b6225e061d00 Mon Sep 17 00:00:00 2001 From: mikhacim Date: Mon, 15 Jun 2026 10:12:43 -0400 Subject: [PATCH] Remove self-signed cert workaround on docs --- content/en/observability_pipelines/sources/_index.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/content/en/observability_pipelines/sources/_index.md b/content/en/observability_pipelines/sources/_index.md index 48d83ed2059..c4f1490557a 100644 --- a/content/en/observability_pipelines/sources/_index.md +++ b/content/en/observability_pipelines/sources/_index.md @@ -146,16 +146,7 @@ Instead of using a self-signed certificate, Datadog recommends the following: 1. Use a certificate signed by Certificate Authority (CA). 2. If you cannot use a CA-signed certificate, use a certificate from [Let's Encrypt][3]. -If you must use a self-signed certificate because the above approaches are not possible, you can configure your environment to trust the self-signed certificate on the Observability Pipelines Worker host. - -
Datadog does not recommend self-signed certificates. They are less secure and are not appropriate for production or internet-facing use. If you must use self-signed certificates, limit usage to internal testing only.
- -For the Worker host to trust the self-signed certificate: - -- On Linux hosts, install the certificate in the OS trust store. -- In Kubernetes, you can either: - - Build a custom container image that includes the certificate. - - Mount the certificate and update the container's trust store manually. +
Datadog does not recommend self-signed certificates. They are less secure and are not appropriate for production or internet-facing use.
## Further reading