From ff419d5996c8fe86cff10f4b9635a22332f0423c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Carlos=20Rodr=C3=ADguez=20Hern=C3=A1ndez?= Date: Thu, 24 Oct 2019 16:07:23 +0200 Subject: [PATCH] [stable/owncloud] Unify and refactor README.md (#18286) Signed-off-by: Carlos Rodriguez Hernandez --- stable/owncloud/Chart.yaml | 2 +- stable/owncloud/README.md | 8 +++++--- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/stable/owncloud/Chart.yaml b/stable/owncloud/Chart.yaml index 0fca91930e..76e4616c23 100644 --- a/stable/owncloud/Chart.yaml +++ b/stable/owncloud/Chart.yaml @@ -1,6 +1,6 @@ apiVersion: v1 name: owncloud -version: 6.2.7 +version: 6.2.8 appVersion: 10.2.1 description: A file sharing server that puts the control and security of your own data back into your hands. keywords: diff --git a/stable/owncloud/README.md b/stable/owncloud/README.md index bb9d673aff..98d6e6fab7 100644 --- a/stable/owncloud/README.md +++ b/stable/owncloud/README.md @@ -31,7 +31,7 @@ To install the chart with the release name `my-release`: $ helm install --name my-release stable/owncloud ``` -The command deploys ownCloud on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. +The command deploys ownCloud on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation. > **Tip**: List all releases using `helm list` @@ -45,7 +45,7 @@ $ helm delete my-release The command removes all the Kubernetes components associated with the chart and deletes the release. -## Configuration +## Parameters The following table lists the configurable parameters of the ownCloud chart and their default values. @@ -141,6 +141,8 @@ $ helm install --name my-release -f values.yaml stable/owncloud > **Tip**: You can use the default [values.yaml](values.yaml) +## Configuration and installation details + ### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/) It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image. @@ -153,7 +155,7 @@ The [Bitnami ownCloud](https://github.com/bitnami/bitnami-docker-owncloud) image Persistent Volume Claims are used to keep the data across deployments. There is a [known issue](https://github.com/kubernetes/kubernetes/issues/39178) in Kubernetes Clusters with EBS in different availability zones. Ensure your cluster is configured properly to create Volumes in the same availability zone where the nodes are running. Kuberentes 1.12 solved this issue with the [Volume Binding Mode](https://kubernetes.io/docs/concepts/storage/storage-classes/#volume-binding-mode). -See the [Configuration](#configuration) section to configure the PVC or to disable persistence. +See the [Parameters](#parameters) section to configure the PVC or to disable persistence. ## Upgrading