@@ -43,7 +43,7 @@ make environment.dev.kind
43
43
44
44
This will create a ` kind ` cluster (or re-use an existing one) using the system's
45
45
local container runtime and deploy the development stack into the ` default `
46
- namespace.
46
+ namespace.
47
47
48
48
There are several ways to access the gateway:
49
49
@@ -56,15 +56,15 @@ $ kubectl --context kind-gie-dev port-forward service/inference-gateway 8080:80
56
56
> ** Warning** : This method doesn't work on ` podman ` correctly, as ` podman ` support
57
57
> with ` kind ` is not fully implemented yet.
58
58
``` sh
59
- # Determine the k8s node address
59
+ # Determine the k8s node address
60
60
$ kubectl --context kind-gie-dev get node -o yaml | grep address
61
61
# The service is accessible over port 80 of the worker IP address.
62
62
```
63
63
64
64
** LoadBalancer**
65
65
66
66
``` sh
67
- # Install and run cloud-provider-kind:
67
+ # Install and run cloud-provider-kind:
68
68
$ go install sigs.k8s.io/cloud-provider-kind@latest && cloud-provider-kind &
69
69
$ kubectl --context kind-gie-dev get service inference-gateway
70
70
# Wait for the LoadBalancer External-IP to become available. The service is accessible over port 80.
@@ -250,3 +250,20 @@ make environment.dev.kubernetes
250
250
```
251
251
252
252
And test the changes.
253
+
254
+ ### Cleanup Environment
255
+
256
+ To clean up the development environment and remove all deployed resources in your namespace, run:
257
+
258
+ ``` sh
259
+ make clean.environment.dev.kubernetes
260
+ ```
261
+
262
+ ** Warning** : This cleanup doesn't remove any custom pull ` Secrets ` you may have added. If you are
263
+ done with this environment, you may want to remove those manually as well.
264
+
265
+ If you also want to remove the namespace entirely, run:
266
+
267
+ ``` sh
268
+ kubectl delete namespace ${NAMESPACE}
269
+ ```
0 commit comments