prometheus-adapter/test
Jayapriya Pai 1b9e052008
chore: update to go 1.24.4 and bump dependencies
k8s dependencies to v0.33.2

chore: upgrade tools versions to latest available

chore: update-generated

chore: update custom-metrics-apiserver to current master

chore: remove deprecated code

Signed-off-by: Jayapriya Pai <janantha@redhat.com>
2025-07-03 16:55:11 +05:30
..
e2e *: update-lint 2024-05-16 14:26:37 +02:00
prometheus-manifests Add initial e2e tests 2023-01-19 12:20:42 +01:00
README.md Add initial e2e tests 2023-01-19 12:20:42 +01:00
run-e2e-tests.sh chore: update to go 1.24.4 and bump dependencies 2025-07-03 16:55:11 +05:30

End-to-end tests

With kind

kind and kubectl are automatically downloaded except if SKIP_INSTALL=true is set. A kind cluster is automatically created before the tests, and deleted after the tests. The prometheus-adapter container image is build locally and imported into the cluster.

KIND_E2E=true make test-e2e

With an existing Kubernetes cluster

If you already have a Kubernetes cluster, you can use:

KUBECONFIG="/path/to/kube/config" REGISTRY="my.registry/prefix" make test-e2e
  • The cluster should not have a namespace prometheus-adapter-e2e. The namespace will be created and deleted as part of the E2E tests.
  • KUBECONFIG is the path of the kubeconfig file. Optional, defaults to ${HOME}/.kube/config
  • REGISTRY is the image registry where the container image should be pushed. Required.

Additional environment variables

These environment variables may also be used (with any non-empty value):

  • SKIP_INSTALL: skip the installation of kind and kubectl binaries;
  • SKIP_CLEAN_AFTER: skip the deletion of resources (Kind cluster or Kubernetes namespace) and of the temporary directory .e2e;
  • CLEAN_BEFORE: clean before running the tests, e.g. if SKIP_CLEAN_AFTER was used on the previous run.