Skip to content

Commit a6ab7fb

Browse files
committed
Some minor tweaks for asciidoc conformity.
1 parent a44b12a commit a6ab7fb

File tree

3 files changed

+11
-12
lines changed

3 files changed

+11
-12
lines changed

docs/commands.asciidoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -545,6 +545,7 @@ The load configuration file has the following YAML attributes:
545545
.Load Configuration File Definitions
546546
[width="90%",cols="m,2",frame="topbot",options="header"]
547547
|======================
548+
|Attribute | Description
548549
|COImagePrefix| the pgo-load image prefix to use for the load job
549550
|COImageTag| the pgo-load image tag to use for the load job
550551
|DbDatabase| the database schema to use for loading the data

docs/configuration.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ readonlyuser:testpass:pgoreader
126126

127127
The following list shows the current *pgo* permissions:
128128
.pgo Permissions
129-
[width="60%",frame="topbot",options="header,footer"]
129+
[width="60%",frame="topbot",options="header"]
130130
|======================
131131
|Permission | Description
132132
|ShowCluster | allow *pgo show cluster*

docs/design.asciidoc

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,6 @@
22
:toc:
33
v2.6, {docdate}
44

5-
6-
image::crunchy_logo.png?raw=true[]
7-
85
== Reference Architecture
96

107
So, what does the Postgres Operator actually deploy
@@ -127,7 +124,7 @@ kubectl get pod -o wide
127124
....
128125

129126
When you scale up a Cluster and add a replica, the scaling will
130-
take into account the use of "--node-name". If it sees that a
127+
take into account the use of ``--node-name''. If it sees that a
131128
cluster was created with a specific node name, then the replica
132129
Deployment will add an affinity rule to attempt to schedule
133130
the replica on a different node than the node the primary is
@@ -212,13 +209,14 @@ that gets mounted into */operator-conf* within the operator pod.
212209
The directory structure of the strategy templates is as
213210
follows:
214211
....
215-
├── backup-job.json
216-
├── cluster
217-
│   └── 1
218-
│   ├── cluster-deployment-1.json
219-
│   ├── cluster-replica-deployment-1.json
220-
│   └── cluster-service-1.json
221-
├── pvc.json
212+
|-- backup-job.json
213+
|-- cluster
214+
| |-- 1
215+
| |-- cluster-deployment-1.json
216+
| |-- cluster-replica-deployment-1.json
217+
| |-- cluster-service-1.json
218+
|
219+
|-- pvc.json
222220
....
223221

224222
In this structure, each strategy's templates live in a subdirectory

0 commit comments

Comments
 (0)