Install Synthetics for Dual Stack using Kubernetes

Validate your infrastructure

Before proceeding, verify that your Kubernetes cluster and underlying infrastructure support Dual Stack networking.

1. Test IPv6 connectivity from your host by running ping6 ipv6.google.com or ping -6 ipv6.google.com, or the equivalent command for your machine.

2. Verify Kubernetes cluster Dual Stack support:

   bash

   コピー

   $
   kubectl get nodes -o jsonpath='{.items[*].status.addresses[?(@.type=="InternalIP")].address}'

   This should return both IPv4 and IPv6 addresses if your cluster is Dual Stack-enabled.

3. Check Docker Dual Stack configuration (if applicable):

   bash

   コピー

   $
   docker network inspect bridge | grep IPv6

Verify Docker is ready for Dual Stack

If your Kubernetes cluster runs on Docker (such as Minikube, kind, or Docker Desktop), ensure Docker is configured to handle both IPv4 and IPv6 traffic. To verify that Docker has IPv6 enabled, run:

$
docker info | grep -i ipv6

The output should confirm that IPv6 is enabled. If it is not, refer to the Docker documentation to enable Dual Stack support before proceeding.

Install with Helm

Deploy the Synthetics job manager using the New Relic Helm chart.

1. Add the New Relic Helm repository:

   bash

   コピー

   $
   helm repo add YOUR_REPO_NAME https://helm-charts.newrelic.com
   $
   helm repo update

2. Install the Synthetics job manager:

   bash

   コピー

   $
   helm install YOUR_JOB_MANAGER_NAME YOUR_REPO_NAME/synthetics-job-manager \
   >
     -n YOUR_NAMESPACE \
   >
     --set synthetics.privateLocationKey=YOUR_PRIVATE_LOCATION_KEY

3. Confirm the pods are up and running:

   bash

   コピー

   $
   kubectl get -n YOUR_NAMESPACE pods

Verify installation

Confirm that your Synthetics job manager can access both IPv4 and IPv6 resources.

1. Check pod status:

   bash

   コピー

   $
   kubectl get pods -n YOUR_NAMESPACE

   All pods should show a Running status.

2. View job manager logs:

   bash

   コピー

   $
   kubectl logs -n YOUR_NAMESPACE <job-manager-pod-name>

3. Test Dual Stack connectivity from within a pod:

   bash

   コピー

   $
   # Test IPv6
   $
   kubectl exec -n YOUR_NAMESPACE <pod-name> -- curl -6 -v http://ipv6.google.com
   $
   
   $
   # Test IPv4
   $
   kubectl exec -n YOUR_NAMESPACE <pod-name> -- curl -4 -v http://google.com

   If both curl commands succeed, your Dual Stack configuration is working correctly.

4. Verify the private location status in the New Relic UI by going to one.newrelic.com > All capabilities > Synthetic monitoring > Private locations. Your private location should show as healthy.