From 7395531df797b413de5d16710d00290336709d57 Mon Sep 17 00:00:00 2001 From: Bruno Bressi Date: Sat, 3 Feb 2024 22:06:20 +0100 Subject: [PATCH] chore: unordered list formatting fixed Signed-off-by: Bruno Bressi --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index c64646f..4db6b2f 100644 --- a/README.md +++ b/README.md @@ -152,15 +152,15 @@ make test-e2e The E2E tests require a running kubernetes cluster. Currently, the namespace and webhook are deployed via helper make targets. To run the tests the following is required: -- docker -- cosign (v2) +* docker +* cosign (v2) To run the E2E tests, the following steps are required (in order): -- create a k3d local cluster for the tests and a local iamge registry (`make e2e-cluster`) -- signing keys are generated (`make e2e-keys`) -- a new `cosignwebhook` image is build and signed with a temp key (`make e2e-images`) -- the image is pushed to a local registry & deployed to the test cluster (`make e2e-deploy`) +* create a k3d local cluster for the tests and a local iamge registry (`make e2e-cluster`) +* signing keys are generated (`make e2e-keys`) +* a new `cosignwebhook` image is build and signed with a temp key (`make e2e-images`) +* the image is pushed to a local registry & deployed to the test cluster (`make e2e-deploy`) To do all of the above, simply run `make e2e-prep`. Each step should also be able to be executed individually. To clean up the E2E setup, run `make e2e-cleanup`. This will delete everything created by the E2E preparation.