Skip to content

Commit 232e708

Browse files
authored
fix: Update deploy-using-helm.md nms => nim (#687)
1 parent a1263f9 commit 232e708

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

content/nim/deploy/kubernetes/deploy-using-helm.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -61,23 +61,23 @@ Make sure there are no extra characters or spaces when copying the JWT token. Th
6161
### Kubernetes
6262

6363
```shell
64-
kubectl create namespace nms
64+
kubectl create namespace nim
6565
kubectl create secret docker-registry regcred \
6666
--docker-server=private-registry.nginx.com \
6767
--docker-username=<NGINX JWT Token> \
6868
--docker-password=none \
69-
-n nms
69+
-n nim
7070
```
7171

7272
### OpenShift
7373

7474
```shell
75-
oc new-project nms && \
75+
oc new-project nim && \
7676
oc create secret docker-registry regcred \
7777
--docker-server=private-registry.nginx.com \
7878
--docker-username=<NGINX JWT Token> \
7979
--docker-password=none \
80-
-n nms
80+
-n nim
8181
```
8282

8383
{{< call-out "note" "Note" >}}
@@ -91,13 +91,13 @@ As a best practice, you can delete the JWT token and clear your shell history af
9191
- Kubernetes
9292

9393
```shell
94-
kubectl get secret regcred --output=yaml -n nms
94+
kubectl get secret regcred --output=yaml -n nim
9595
```
9696

9797
- OpenShift
9898

9999
```shell
100-
oc get secret regcred --output=yaml -n nms
100+
oc get secret regcred --output=yaml -n nim
101101
```
102102

103103
You can now use this secret for Helm deployments and point the chart to the private registry.

0 commit comments

Comments
 (0)