> ## Documentation Index
> Fetch the complete documentation index at: https://docs.drdroid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Service Topology

## Automated Discovery of Service Topology from K8s using Proxy Agent

If you're using k8s, added context of your inter-service interactions can be made available to the agent automatically.

Our [proxy agent](https://github.com/DrDroidLab/drd-vpc-agent) maps your network calls within and external to the cluster, then creates a condensed service map that is accessible to the agent in real-time.

### How this works?

Our proxy agent ships with a network mapper that maps the complete topology of your Kubernetes cluster.
Once you clone the agent repository, run the following command.

```shell theme={null}
./deploy_k8s.sh <API_TOKEN>
```

In case you don't want to install the network mapper, disable its installation using a simple flag.

```shell theme={null}
./deploy_k8s.sh <API_TOKEN> --no-network-mapper
```

**⚠️ Important**: Deploying the network mapper will significantly improve the agent's ability to provide comprehensive insights about your infrastructure. It's strongly recommended to keep it enabled unless you have specific security or resource constraints.

#### For ArgoCD Users

The configuration flags are also available in `helm/values.yaml`:

```yaml theme={null}
# Network Mapper Configuration
networkMapper:
  enabled: true  # Set to false to disable
```

#### Deployment Details

* The agent will be installed in the namespace 'drdroid' by default
* Network mapper components are deployed to 'otterize-system' namespace (when enabled)
* Agent will only have read access to the cluster and will be able to fetch the metrics from the cluster