From 7dde50dbee08830b398f5babb3aeb374b01caee4 Mon Sep 17 00:00:00 2001 From: AdamDang Date: Tue, 1 May 2018 03:08:17 +0800 Subject: [PATCH] Typo fix in gcloud-sqlproxy/README.md:"on on"->"on" (#5197) * Add version for gcloud-sqlproxy version: 0.3.3 * Typo fix in gcloud-sqlproxy/README.md:"on on"->"on" Typo fix in gcloud-sqlproxy/README.md:"on on"->"on" --- stable/gcloud-sqlproxy/Chart.yaml | 2 +- stable/gcloud-sqlproxy/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/stable/gcloud-sqlproxy/Chart.yaml b/stable/gcloud-sqlproxy/Chart.yaml index de78c3e058..8bafd61780 100644 --- a/stable/gcloud-sqlproxy/Chart.yaml +++ b/stable/gcloud-sqlproxy/Chart.yaml @@ -1,5 +1,5 @@ name: gcloud-sqlproxy -version: 0.3.2 +version: 0.3.3 appVersion: 1.11 description: Google Cloud SQL Proxy keywords: diff --git a/stable/gcloud-sqlproxy/README.md b/stable/gcloud-sqlproxy/README.md index 28ced78f14..6f77f21e84 100644 --- a/stable/gcloud-sqlproxy/README.md +++ b/stable/gcloud-sqlproxy/README.md @@ -35,7 +35,7 @@ $ helm upgrade pg-sqlproxy stable/gcloud-sqlproxy --namespace sqlproxy \ Replace Postgres/MySQL host with: if access is from the same namespace with `pg-sqlproxy-gcloud-sqlproxy` or if it is from a different namespace with `pg-sqlproxy-gcloud-sqlproxy.sqlproxy`, the rest database connections settings do not have to be changed. > **Tip**: List all releases using `helm list` -> **Tip**: If you encounter a YAML parse error on on `gcloud-sqlproxy/templates/secrets.yaml`, you might need to set `-w 0` option to `base64` command. +> **Tip**: If you encounter a YAML parse error on `gcloud-sqlproxy/templates/secrets.yaml`, you might need to set `-w 0` option to `base64` command. > **Tip**: If you are using a MySQL instance, you may want to replace `pg-sqlproxy` with `mysql-sqlproxy` and `5432` with `3306`. ## Uninstalling the Chart