Reconsider patroni_use_kubernetes default to true.

It will not break existing setups, since it will be overriden by
the non-empty etcd_host parameter.
This commit is contained in:
Oleksii Kliukin 2018-05-24 17:13:45 +02:00
parent a26d16999a
commit 76be1605b2
1 changed files with 1 additions and 1 deletions

View File

@ -70,7 +70,7 @@ type Config struct {
WatchedNamespace string `name:"watched_namespace"` // special values: "*" means 'watch all namespaces', the empty string "" means 'watch a namespace where operator is deployed to' WatchedNamespace string `name:"watched_namespace"` // special values: "*" means 'watch all namespaces', the empty string "" means 'watch a namespace where operator is deployed to'
EtcdHost string `name:"etcd_host" default:"etcd-client.default.svc.cluster.local:2379"` EtcdHost string `name:"etcd_host" default:"etcd-client.default.svc.cluster.local:2379"`
PatroniUseKubernetes bool `name:"patroni_use_kubernetes" default:"false"` PatroniUseKubernetes bool `name:"patroni_use_kubernetes" default:"true"`
DockerImage string `name:"docker_image" default:"registry.opensource.zalan.do/acid/spiloprivate-9.6:1.2-p4"` DockerImage string `name:"docker_image" default:"registry.opensource.zalan.do/acid/spiloprivate-9.6:1.2-p4"`
// default name `operator` enables backward compatibility with the older ServiceAccountName field // default name `operator` enables backward compatibility with the older ServiceAccountName field
PodServiceAccountName string `name:"pod_service_account_name" default:"operator"` PodServiceAccountName string `name:"pod_service_account_name" default:"operator"`