kubernetes

mirror of https://github.com/outbackdingo/kubernetes.git synced 2026-01-27 10:19:35 +00:00

Files

Ed Bartosh 41013e7bf0 e2e_dra: use latest release if stable doesn't exist

This change updates the DRA upgrade/downgrade test to attempt
downloading the "latest" Kubernetes release if the "stable" release
entry point is not available.

This should fix test failures for the time just before the release,
when master is switched to the next release, but stable release URL
is not yet updated.

2025-08-18 10:23:42 +03:00

gtesting_test.go

…

README.md

…

run.sh

…

upgradedowngrade_test.go

e2e_dra: use latest release if stable doesn't exist

2025-08-18 10:23:42 +03:00

README.md

This directory contains a testsuite with automatic upgrade/downgrade tests for DRA. Conceptually this is like an integration test, in the sense that it starts/stops cluster components and runs tests against them.

The difference is that it starts Kubernetes components by running the actual binaries, relying on local-up-cluster.sh for the logic and configuration steps. Because local-up-cluster.sh needs additional permissions and preparations on the host, the test cannot run in "make test-integration" and just skips itself there.

To run it:

Make sure that hack/local-up-cluster.sh works:
- sudo must work
- Set env variables as necessary for your environment.
Ensure that /var/lib/kubelet/plugins, /var/lib/kubelet/plugins_registry, and /var/run/cdi are writable.
Build binaries with make.
Export KUBERNETES_SERVER_BIN_DIR=$(pwd)/_output/local/bin/linux/amd64 (or whatever is your GOOS/GOARCH and output directory).
Optional: export KUBERNETES_SERVER_CACHE_DIR=$(pwd)/_output/local/bin/linx/amd64/cache-dir to reuse downloaded release binaries across test invocations.
Optional: set ARTIFACTS to store component log files persistently. Otherwise a test tmp directory is used.

Invoke as a Go test (no need for the ginkgo CLI), for example:

  go test -v -count=1 -timeout=1h ./test/e2e_dra -args -ginkgo.v
  dlv test ./test/e2e_dra -- -ginkgo.v
  make test KUBE_TIMEOUT=-timeout=1h WHAT=test/e2e_dra FULL_LOG=true KUBE_TEST_ARGS="-count=1 -args -ginkgo.v"

make test instead of make test-integration is intentional: local-up-cluster.sh itself wants to start etcd. -count=1 ensures that test runs each time it is invoked. -v and -ginkgo.v make the test output visible while the test runs.

To simplify starting from scratch, ./test/e2e_dra/run.sh cleans up, sets permissions, and then invokes whatever command is specified on the command line:

 ./test/e2e_dra/run.sh go test ./test/e2e_dra

The test is implemented as a Ginkgo suite because that allows reusing the same helper code as in E2E tests. Long-term the goal is to port that helper code to ktesting, support ktesting in test/e2e, and turn this test into a normal Go test.