From a19701dea4d4fb108bbaea9ba32d6dc5e0b792e2 Mon Sep 17 00:00:00 2001 From: chenhuan12 Date: Thu, 30 Mar 2017 15:06:30 +0800 Subject: [PATCH] fix typo fix typo --- docs/user-guide/service-accounts.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/user-guide/service-accounts.md b/docs/user-guide/service-accounts.md index 44c5a3610e..4a493aacf4 100644 --- a/docs/user-guide/service-accounts.md +++ b/docs/user-guide/service-accounts.md @@ -55,7 +55,7 @@ metadata: name: build-robot EOF $ 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: @@ -111,7 +111,7 @@ metadata: type: kubernetes.io/service-account-token EOF $ 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. @@ -143,8 +143,8 @@ Next, verify it has been created. For example: ```shell $ kubectl get secrets myregistrykey -NAME TYPE DATA -myregistrykey kubernetes.io/.dockerconfigjson 1 +NAME TYPE DATA AGE +myregistrykey   kubernetes.io/.dockerconfigjson   1       1d ``` Next, read/modify/write the service account for the namespace to use this secret as an imagePullSecret.