update info (#30469)

Author: maycmlee

layouts/shortcodes/observability_pipelines/log_source_configuration/datadog_agent.en.md

@@ -10,7 +10,7 @@ observability_pipelines_worker:
 
 For CloudFormation installs, use the `LoadBalancerDNS` CloudFormation output for the URL.
 
-For Kubernetes installs, you can use the internal DNS record of the Observability Pipelines Worker service. For example: `opw-observability-pipelines-worker.default.svc.cluster.local`.
+For Kubernetes installs, you can use the internal DNS record of the Observability Pipelines Worker service. For example: `http://opw-observability-pipelines-worker.default.svc.cluster.local:<PORT>`.
 
 After you restart the Agent, your observability data should be going to the Worker, processed by the pipeline, and delivered to Datadog.
 

layouts/shortcodes/observability_pipelines/log_source_configuration/datadog_agent_kubernetes.en.md

@@ -11,7 +11,7 @@ datadog:
 
 `<OPW_HOST>` is the IP/URL of the host (or load balancer) associated with the Observability Pipelines Worker.
 
-For Kubernetes installs, you can use the internal DNS record of the Observability Pipelines Worker service. For example: `opw-observability-pipelines-worker.default.svc.cluster.local`.
+For Kubernetes installs, you can use the internal DNS record of the Observability Pipelines Worker service. For example: `http://opw-observability-pipelines-worker.default.svc.cluster.local:<PORT>`.
 
 [1021]: https://github.com/DataDog/helm-charts/blob/main/charts/datadog/values.yaml
 [1022]: https://docs.datadoghq.com/agent/guide/environment-variables/