Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: ignore #1600

Closed
wants to merge 1 commit into from
Closed

WIP: ignore #1600

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion docs/book/src/reference/envtest.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,19 @@ err = testEnv.Stop()
Logs from the test runs are prefixed with `test-env`.

### Configuring your test control plane
You can use environment variables and/or flags to specify the `api-server` and `etcd` setup within your integration tests.

You can use environment variables and/or flags to specify the `kubectl`, `api-server` and `etcd` setup within your
integration tests. The location of the binaries which will be used by the [EnvtTest][envtest] is done due the following environment
variables. See:

```shell
$ export TEST_ASSET_KUBECTL=<kubectl-bin-path>
$ export TEST_ASSET_KUBE_APISERVER=<api-server-bin-path>
$ export TEST_ASSET_ETCD=<etcd-bin-path>
```

Note that `kubebuilder` scaffold in your Makefile the `setupenvtest` target which download the binaries and setup it.

#### Environment Variables

| Variable name | Type | When to use |
Expand Down Expand Up @@ -71,3 +82,4 @@ expectedOwnerReference := v1.OwnerReference{
}
Expect(deployment.ObjectMeta.OwnerReferences).To(ContainElement(expectedOwnerReference))
```
[envtest]: https://godoc.org/sigs.k8s.io/controller-runtime/pkg/envtest