Update configs with username followed by password

The way that the document currently flows and how we typically perceive credentials, we usually set our username first followed by the password.

Seeing the configuration first set password then username seems counter-intuitive.  There is nothing wrong with the docs, it is just clearer to view username=>password.
This commit is contained in:
Oleg Shalygin 2017-01-04 16:23:20 -08:00 committed by GitHub
parent 88a9aa9c46
commit 757dd707b6
1 changed files with 2 additions and 2 deletions

View File

@ -113,8 +113,8 @@ metadata:
name: mysecret
type: Opaque
data:
password: MWYyZDFlMmU2N2Rm
username: YWRtaW4=
password: MWYyZDFlMmU2N2Rm
```
The data field is a map. Its keys must match
@ -142,8 +142,8 @@ Get back the secret created in the previous section:
$ kubectl get secret mysecret -o yaml
apiVersion: v1
data:
password: MWYyZDFlMmU2N2Rm
username: YWRtaW4=
password: MWYyZDFlMmU2N2Rm
kind: Secret
metadata:
creationTimestamp: 2016-01-22T18:41:56Z