From 38b2e11634c01346b295696f82c9d52023d09cb2 Mon Sep 17 00:00:00 2001 From: Satnam Singh Date: Sun, 19 Jul 2015 01:15:02 +0100 Subject: [PATCH] Fix console output in production-pods.md --- docs/user-guide/production-pods.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/user-guide/production-pods.md b/docs/user-guide/production-pods.md index 64326d0b000..1d657e2add6 100644 --- a/docs/user-guide/production-pods.md +++ b/docs/user-guide/production-pods.md @@ -107,7 +107,7 @@ data: As with other resources, this secret can be instantiated using `create` and can be viewed with `get`: -```bash +```console $ kubectl create -f ./secret.yaml secrets/mysecret $ kubectl get secrets @@ -158,7 +158,7 @@ Secrets can also be used to pass [image registry credentials](images.md#using-a- First, create a `.dockercfg` file, such as running `docker login `. Then put the resulting `.dockercfg` file into a [secret resource](secrets.md). For example: -``` +```console $ docker login Username: janedoe Password: ●●●●●●●●●●● @@ -189,7 +189,7 @@ secrets/myregistrykey Now, you can create pods which reference that secret by adding an `imagePullSecrets` section to a pod definition. -``` +```yaml apiVersion: v1 kind: Pod metadata: @@ -367,7 +367,7 @@ spec: The message is recorded along with the other state of the last (i.e., most recent) termination: -```bash +```console $ kubectl create -f ./pod.yaml pods/pod-w-message $ sleep 70