From 3818e4e229544cb9917ffcb9217825d225424eb5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Carlos=20Rodr=C3=ADguez=20Hern=C3=A1ndez?= Date: Fri, 16 Mar 2018 20:52:42 +0100 Subject: [PATCH] [stable/wordpress] Fix some typos (#4208) * [stable/ghost] Fix some typos * [stable/wordpress] Fix some typos * Revert "[stable/ghost] Fix some typos" This reverts commit fe3bc14a3ec611dc4f455a936128b2c771579c40. --- stable/wordpress/Chart.yaml | 2 +- stable/wordpress/README.md | 18 ++++++++++-------- 2 files changed, 11 insertions(+), 9 deletions(-) diff --git a/stable/wordpress/Chart.yaml b/stable/wordpress/Chart.yaml index 878bb8efaf..40974ce7da 100644 --- a/stable/wordpress/Chart.yaml +++ b/stable/wordpress/Chart.yaml @@ -1,5 +1,5 @@ name: wordpress -version: 0.8.13 +version: 0.8.14 appVersion: 4.9.4 description: Web publishing platform for building blogs and websites. icon: https://bitnami.com/assets/stacks/wordpress/img/wordpress-stack-220x234.png diff --git a/stable/wordpress/README.md b/stable/wordpress/README.md index 025d446b93..6ff3d903c4 100644 --- a/stable/wordpress/README.md +++ b/stable/wordpress/README.md @@ -43,7 +43,7 @@ The command removes all the Kubernetes components associated with the chart and ## Configuration -The following tables lists the configurable parameters of the WordPress chart and their default values. +The following tables list the configurable parameters of the WordPress chart and their default values. | Parameter | Description | Default | | ------------------------------- | ------------------------------- | ---------------------------------------------------------- | @@ -101,7 +101,7 @@ $ helm install --name my-release \ stable/wordpress ``` -The above command sets the WordPress administrator account username and password to `admin` and `password` respectively. Additionally it sets the MariaDB `root` user password to `secretpassword`. +The above command sets the WordPress administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MariaDB `root` user password to `secretpassword`. Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, @@ -139,16 +139,17 @@ the ingress controller to service your WordPress application. To enable ingress integration, please set `ingress.enabled` to `true` ### Hosts + Most likely you will only want to have one hostname that maps to this -WordPress installation, however it is possible to have more than one +WordPress installation, however, it is possible to have more than one host. To facilitate this, the `ingress.hosts` object is an array. For each item, please indicate a `name`, `tls`, `tlsSecret`, and any `annotations` that you may want the ingress controller to know about. -Indicating TLS will cause WordPress to generate HTTPS urls, and +Indicating TLS will cause WordPress to generate HTTPS URLs, and WordPress will be connected to at port 443. The actual secret that -`tlsSecret` references does not have to be generated by this chart. +`tlsSecret` references do not have to be generated by this chart. However, please note that if TLS is enabled, the ingress record will not work until this secret exists. @@ -158,12 +159,13 @@ document does a good job of indicating which annotation is supported by many popular ingress controllers. ### TLS Secrets + This chart will facilitate the creation of TLS secrets for use with the -ingress controller, however this is not required. There are three +ingress controller, however, this is not required. There are three common use cases: -* helm generates / manages certificate secrets -* user generates / manages certificates separately +* helm generates/manages certificate secrets +* user generates/manages certificates separately * an additional tool (like [kube-lego](https://kubeapps.com/charts/stable/kube-lego)) manages the secrets for the application