This document was translated by ChatGPT

1. Introduction

DeepFlow Agent can be deployed as a Sidecar within a Serverless Pod. Assuming you have already deployed DeepFlow Server in a K8s cluster, this chapter explains how to monitor applications within a Serverless Pod.

2. Deployment Topology

3. Deploy deepflow-agent

Modify the value file to deploy deepflow-agent as a daemonset and inject it as a sidecar, then obtain the clusterNAME through deepflow-ctl domain list.

cat << EOF > values-custom.yaml
deployComponent:
- "daemonset"
- "watcher"
tke_sidecar: true
clusterNAME: $clusterNAME  # FIXME: domain name
EOF

helm install deepflow-agent -n deepflow deepflow/deepflow-agent --create-namespace \
  -f values-custom.yaml

If you do not want the sidecar form of deepflow-agent to take on the role of list-watch apiserver, it is recommended to deploy a separate deepflow-agent deployment to synchronize K8s resources. For specific methods, refer to Deploy DeepFlow Agent in Deployment Mode.

4. Next Steps

• Universal Service Map - Experience DeepFlow's AutoMetrics Capability
• Distributed Tracing - Experience DeepFlow's AutoTracing Capability
• Eliminate Data Silos - Learn About DeepFlow's AutoTagging and SmartEncoding Capabilities
• Say Goodbye to High Maintenance - Integrate Prometheus and Other Metric Data
• Full-Stack Distributed Tracing - Integrate OpenTelemetry and Other Tracing Data