consistent order of sample yaml file (#13875)

changed the order in sample yaml file.
Resole the issue #13862
This commit is contained in:
Vageesha17 2019-04-19 13:33:55 +05:30 committed by Kubernetes Prow Robot
parent 126f9a3a0d
commit 413a4c5afc
1 changed files with 4 additions and 4 deletions

View File

@ -715,8 +715,8 @@ Now we can create a pod which references the secret with the ssh key and
consumes it in a volume: consumes it in a volume:
```yaml ```yaml
kind: Pod
apiVersion: v1 apiVersion: v1
kind: Pod
metadata: metadata:
name: secret-test-pod name: secret-test-pod
labels: labels:
@ -851,8 +851,8 @@ one called, say, `prod-user` with the `prod-db-secret`, and one called, say,
`test-user` with the `test-db-secret`. Then, the pod spec can be shortened to, for example: `test-user` with the `test-db-secret`. Then, the pod spec can be shortened to, for example:
```yaml ```yaml
kind: Pod
apiVersion: v1 apiVersion: v1
kind: Pod
metadata: metadata:
name: prod-db-client-pod name: prod-db-client-pod
labels: labels:
@ -870,15 +870,15 @@ In order to make piece of data 'hidden' (i.e., in a file whose name begins with
make that key begin with a dot. For example, when the following secret is mounted into a volume: make that key begin with a dot. For example, when the following secret is mounted into a volume:
```yaml ```yaml
kind: Secret
apiVersion: v1 apiVersion: v1
kind: Secret
metadata: metadata:
name: dotfile-secret name: dotfile-secret
data: data:
.secret-file: dmFsdWUtMg0KDQo= .secret-file: dmFsdWUtMg0KDQo=
--- ---
kind: Pod
apiVersion: v1 apiVersion: v1
kind: Pod
metadata: metadata:
name: secret-dotfiles-pod name: secret-dotfiles-pod
spec: spec: