Skip to content

Commit 3344444

Browse files
committed
Update README
1 parent ada29c7 commit 3344444

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

tests/README.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -102,8 +102,8 @@ make update-firewall-with-local-ip
102102

103103
### Step 2 - Build and Load Images
104104

105-
Loading the images only applies to a `kind` cluster. If using a cloud provider, you will need to tag and push
106-
your images to a registry that is accessible from that cloud provider.
105+
Loading the images only applies to a `kind` cluster. If using GKE, you will need to tag and push
106+
your images to a registry that is accessible from GKE.
107107

108108
```makefile
109109
make build-images load-images TAG=$(whoami)
@@ -115,6 +115,8 @@ Or, to build NGF with NGINX Plus enabled (NGINX Plus cert and key must exist in
115115
make build-images-with-plus load-images-with-plus TAG=$(whoami)
116116
```
117117

118+
When building images to run on GKE, you'll need to specify `GOARCH=amd64` in the build command if your local system doesn't default to that architecture.
119+
118120
For the telemetry test, which requires a OTel collector, build an image with the following variables set:
119121

120122
```makefile
@@ -314,6 +316,8 @@ incremental changes and copy your local changes to the VM to test, you can run
314316
make sync-files-to-vm
315317
```
316318

319+
> Note: if just running longevity tests, skip to the [Longevity section](#longevity-testing).
320+
317321
To set up the GCP environment with the router and VM and then run the tests, run the following command:
318322

319323
```makefile

0 commit comments

Comments
 (0)