-
Notifications
You must be signed in to change notification settings - Fork 8
/
vars.yml
53 lines (53 loc) · 2.24 KB
/
vars.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
---
dcs: "etcd"
#dcs_server_ips:
# - 10.0.0.1
# - 10.0.0.2
dcs_port:
consul: 8500
zookeeper: 2181
etcd: 2379
etcd3: 2379
consul_datacenter: "global"
consul_group: "consul"
# Whether to use the regular or testing pgdg APT repository, values can be
# `pgdg' (default) or `pgdg-testing'.
#pgdg_repo: pgdg-testing
postgresql_cluster_name: "main"
postgresql_major_version: "14"
postgresql_port: "5432"
# PostgreSQL base directory. If not set, @DATADIR_BASE@ is used, which is
# evaluated by pg_createconfig_patroni to either the default
# (/var/lib/postgresql) or what the data_directory variable (without %v/%c) in
# /etc/postgresql-common/createcluster.conf is set to.
#postgresql_data_dir_base: "/var/lib/postgresql"
patroni_replication_user: "replicator"
patroni_replication_pass: "replicator"
# Password for the postgres superuser. Usually setting a password is
# discouraged, and socket-based peer authentication to the local postgres
# instance should be used instead. However, patroni_postgres_pass needs to be
# set on PostgresSQL 10 and earlier if pg_rewind is to be used to get diverged
# former primaries back online without a full re-clone.
patroni_postgres_pass: ""
# from Postgresql 11, pg_rewind can use a regular user with the appropriate
# fine-grained permissions. If set, Patroni will setup the user and its
# permissions. Note: "pg_rewind" is a reserved role and cannot be used.
patroni_rewind_user: "postgres_rewind"
patroni_rewind_pass: "postgres_rewind"
# The Patroni REST port
patroni_port: 8008
# vip-manager will manage the vip on each node if set
#vip: "10.0.1.1"
# If HAProxy is to be deployed on one of the servers, add a "[haproxy_server]"
# section to the inventory, make sure "postgresql_port" and "patroni_port" are
# set and uncomment/edit the following HAProxy ports to be used by
# clients/applications:
#haproxy_write_port: 5432
#haproxy_read_port: 5433
# Uncomment this if the primary should also get read-only queries
#haproxy_primary_read_scale: "on"
# By default HAProxy uses the "haproxy" user for the read-only health check if
# haproxy_primary_read_scale is enabled. If this user does not exist, error
# messages will be logged in the Postgres log. Alternatively, another can be
# specified:
#haproxy_health_check_user: "haproxy"