You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: test/README.md
+12-2
Original file line number
Diff line number
Diff line change
@@ -2,15 +2,25 @@
2
2
3
3
## Running Vault Helm Acceptance tests
4
4
5
-
The Makefile at the top level of this repo contains a few target that should help with running acceptance tests in your own GKE instance.
5
+
The Makefile at the top level of this repo contains a few target that should help with running acceptance tests in your own GKE instance or in kind cluster.
6
6
7
-
* Set the GOOGLE_CREDENTIALS and CLOUDSDK_CORE_PROJECT variables at the top of the file. GOOGLE_CREDENTIALS should contain the local path to your Google Cloud Platform account credentials in JSON format. CLOUDSDK_CORE_PROJECT should be set to the ID of your GCP project.
7
+
### Running in a GKE cluster
8
+
* Set the `GOOGLE_CREDENTIALS` and `CLOUDSDK_CORE_PROJECT` variables at the top of the file. `GOOGLE_CREDENTIALS` should contain the local path to your Google Cloud Platform account credentials in JSON format. `CLOUDSDK_CORE_PROJECT` should be set to the ID of your GCP project.
8
9
* Run `make test-image` to create the docker image (with dependencies installed) that will be re-used in the below steps.
9
10
* Run `make test-provision` to provision the GKE cluster using terraform.
10
11
* Run `make test-acceptance` to run the acceptance tests in this already provisioned cluster.
11
12
* You can choose to only run certain tests by setting the ACCEPTANCE_TESTS variable and re-running the above target.
12
13
* Run `make test-destroy` when you have finished testing and want to tear-down and remove the cluster.
13
14
15
+
### Running in a kind cluster
16
+
* Run `make test-acceptance LOCAL_ACCEPTANCE_TESTS=true`
17
+
* You can choose to only run certain tests by setting the `ACCEPTANCE_TESTS` variable and re-running the above target.
18
+
* Run `make delete-kind` when you have finished testing and want to tear-down and remove the cluster.
19
+
* You can set an alternate kind cluster name by specifying the `KIND_CLUSTER_NAME` variable for any of the above targets.
20
+
* You can set an alternate K8S version by specifying the `KIND_K8S_VERSION` variable for any of the above targets.
21
+
22
+
See [kind-quick-start](https://kind.sigs.k8s.io/docs/user/quick-start/) if you don't have kind installed on your system.
23
+
14
24
## Running chart verification tests
15
25
16
26
If [chart-verifier](https://github.com/redhat-certification/chart-verifier) is built and available in your PATH, run:
0 commit comments