From 2badcdd39be31c049c23c591d3467a08b9a19b5e Mon Sep 17 00:00:00 2001 From: sixtyeight Date: Fri, 5 May 2017 01:53:54 +0200 Subject: [PATCH 1/2] PostgreSQL secret: typo and copy/paste error --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index a1efb8e1..9322c74f 100644 --- a/README.md +++ b/README.md @@ -144,7 +144,7 @@ This can be externalized to Secrets in yaml format: amq.password: MWYyZDFlMmU2N2Rm ``` -- **PostreSQL** +- **PostgreSQL** ```yaml apiVersion: v1 kind: Secret @@ -154,8 +154,8 @@ This can be externalized to Secrets in yaml format: db: postgres type: Opaque data: - amq.username: dXNlcgo= - amq.password: cGdhZG1pbgo= + pg.username: dXNlcgo= + pg.password: cGdhZG1pbgo= ``` You can select the Secrets to consume in a number of ways: From 3c966b4f41009a2f7cecf24f1ac2e9077f51fadf Mon Sep 17 00:00:00 2001 From: sixtyeight Date: Fri, 5 May 2017 02:37:13 +0200 Subject: [PATCH 2/2] removed superfluous 'we' --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9322c74f..24aaf597 100644 --- a/README.md +++ b/README.md @@ -86,7 +86,7 @@ data: pool.size.max: 16 ``` -Individual properties work fine for most cases but sometimes we yaml is more convinient. In this case we will use a single property named `application.yaml` and embed our yaml inside it: +Individual properties work fine for most cases but sometimes yaml is more convinient. In this case we will use a single property named `application.yaml` and embed our yaml inside it: ```yaml kind: ConfigMap