From 056b2222a5f3998d16d17f6f31b59ed4ab9430c4 Mon Sep 17 00:00:00 2001 From: phobot Date: Tue, 27 Aug 2019 12:28:54 +0300 Subject: [PATCH] fix relative links to manifest files (#655) [minimal](../manifests/minimal-postgres-manifest.yaml) and the [complete](../manifests/complete-postgres-manifest.yaml) Links don't work as the manifests directory is higher in the structure. --- docs/reference/cluster_manifest.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/cluster_manifest.md b/docs/reference/cluster_manifest.md index 7c2839662..edaada9b4 100644 --- a/docs/reference/cluster_manifest.md +++ b/docs/reference/cluster_manifest.md @@ -4,9 +4,9 @@ Individual Postgres clusters are described by the Kubernetes *cluster manifest* that has the structure defined by the `postgresql` CRD (custom resource definition). The following section describes the structure of the manifest and the purpose of individual keys. You can take a look at the examples of the -[minimal](../manifests/minimal-postgres-manifest.yaml) +[minimal](../../manifests/minimal-postgres-manifest.yaml) and the -[complete](../manifests/complete-postgres-manifest.yaml) +[complete](../../manifests/complete-postgres-manifest.yaml) cluster manifests. When Kubernetes resources, such as memory, CPU or volumes, are configured,