Content Comparison

Kloudfuse stack & target both in same VPC and in same K8S cluster (Default)

This is the default scenario. Just use the provided values file for the agent and install.

Kloudfuse stack & target both in same VPC, but in different K8S cluster

Search for _url in the provided file. Wherever found, comment the Default Scenario and uncomment Scenario 1. For the IP address values needed, please see the following steps.

• Get ingress internal IP

  Code Block
  kubectl get svc -n kfuse | grep kfuse-ingress-nginx-controller-internal kfuse-ingress-nginx-controller-internal LoadBalancer 10.53.250.80 10.53.232.3 80:32716/TCP,443:30767/TCP 125m

• replace all settings with _url suffix, for example:

  Code Block
  dd_url: http://10.53.250.80/ingester logs_dd_url: "10.53.250.80:80"

Kloudfuse stack hosted in a different VPC (hosted at “customer.kloudfuse.io”)

Search for _url in the provided filevalues.yaml file provided in the first scenario. Wherever found, comment the Default Scenario and uncomment Scenario 2. Replace the customer.klodufusekloudfuse.io with your custom DNS name entry.

• replace all settings with _url suffix, for example:

  Code Block
  dd_url: http://customer.kloudfuse.io/ingester logs_dd_url: "customer.kloudfuse.io:443"