fix typo
fix typo
This commit is contained in:
@@ -55,7 +55,7 @@ metadata:
|
|||||||
name: build-robot
|
name: build-robot
|
||||||
EOF
|
EOF
|
||||||
$ kubectl create -f /tmp/serviceaccount.yaml
|
$ kubectl create -f /tmp/serviceaccount.yaml
|
||||||
serviceaccounts/build-robot
|
serviceaccount "build-robot" created
|
||||||
```
|
```
|
||||||
|
|
||||||
If you get a complete dump of the service account object, like this:
|
If you get a complete dump of the service account object, like this:
|
||||||
@@ -111,7 +111,7 @@ metadata:
|
|||||||
type: kubernetes.io/service-account-token
|
type: kubernetes.io/service-account-token
|
||||||
EOF
|
EOF
|
||||||
$ kubectl create -f /tmp/build-robot-secret.yaml
|
$ kubectl create -f /tmp/build-robot-secret.yaml
|
||||||
secrets/build-robot-secret
|
secret "build-robot-secret" created
|
||||||
```
|
```
|
||||||
|
|
||||||
Now you can confirm that the newly built secret is populated with an API token for the "build-robot" service account.
|
Now you can confirm that the newly built secret is populated with an API token for the "build-robot" service account.
|
||||||
@@ -143,8 +143,8 @@ Next, verify it has been created. For example:
|
|||||||
|
|
||||||
```shell
|
```shell
|
||||||
$ kubectl get secrets myregistrykey
|
$ kubectl get secrets myregistrykey
|
||||||
NAME TYPE DATA
|
NAME TYPE DATA AGE
|
||||||
myregistrykey kubernetes.io/.dockerconfigjson 1
|
myregistrykey kubernetes.io/.dockerconfigjson 1 1d
|
||||||
```
|
```
|
||||||
|
|
||||||
Next, read/modify/write the service account for the namespace to use this secret as an imagePullSecret.
|
Next, read/modify/write the service account for the namespace to use this secret as an imagePullSecret.
|
||||||
|
|||||||
Reference in New Issue
Block a user