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: tests/README.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,8 +102,8 @@ make update-firewall-with-local-ip
102
102
103
103
### Step 2 - Build and Load Images
104
104
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.
107
107
108
108
```makefile
109
109
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
115
115
make build-images-with-plus load-images-with-plus TAG=$(whoami)
116
116
```
117
117
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
+
118
120
For the telemetry test, which requires a OTel collector, build an image with the following variables set:
119
121
120
122
```makefile
@@ -314,6 +316,8 @@ incremental changes and copy your local changes to the VM to test, you can run
314
316
make sync-files-to-vm
315
317
```
316
318
319
+
> Note: if just running longevity tests, skip to the [Longevity section](#longevity-testing).
320
+
317
321
To set up the GCP environment with the router and VM and then run the tests, run the following command:
0 commit comments