README.md

E2E tests

You can run e2e tests on any cluster, please notice that scraping control plane could be not possible or needing specific values depending on the flavour. The following instructions assume as developing environment Minikube

In order to run e2e tests locally you can do the following

eval $(minikube -p minikube docker-env)
minikube addons enable metrics-server

Note that the control plane flags in e2e-values.yml have been set meeting the minikube specifications.

Then you need to build the binary and the image. Notice that since the Dockerfile includes multiarch support, you may need to set DOCKER_BUILDKIT=1 when running docker build for the TARGETARCH and TARGETOS args to be populated.

GOOS=linux GOARCH=amd64 make compile # Set GOOS and GOARCH explicitly since Dockerfile expects them in the binary name
export  DOCKER_BUILDKIT=1
docker build -t e2e/nri-kubernetes:e2e  .
minikube image load e2e/nri-kubernetes:e2e

Then, include helm needed repositories.

helm repo add newrelic https://helm-charts.newrelic.com
helm repo add kube-state-metrics https://kubernetes.github.io/kube-state-metrics
helm repo update

You need to install the binary https://github.com/newrelic/newrelic-integration-e2e-action/tree/main/newrelic-integration-e2e used in the e2e test

git clone https://github.com/newrelic/newrelic-integration-e2e-action
cd newrelic-integration-e2e-action/newrelic-integration-e2e
go build -o  $GOPATH/bin/newrelic-integration-e2e ./cmd/...

You can now run the e2e tests locally

LICENSE_KEY=${LICENSE_KEY} newrelic-integration-e2e --commit_sha=test-string --retry_attempts=5 --retry_seconds=60 \
	 --account_id=${ACCOUNT_ID} --api_key=${API_KEY} --license_key=${LICENSE_KEY} \
	 --spec_path=./e2e/test-specs.yml --verbose_mode=true --agent_enabled="false"

You may check e2e workflow to have more details about how this is used in development workflow.