/
githubmirror
/
charts
Обзор
Документация
Войти
/
githubmirror
/
charts
Код
Запросы
0
Пакеты
0
Релизы
0
Аналитика
Безопасность
master
stable/stolon/values.yaml
203 строки
5 KB
Tiago Posse
[stable/stolon] Allow password files to be used (#22544)
04 июн 2020, 20:25
Не верифицирован
04 июн 2020, 20:25
6b94992
Код
Авторство
О чём код?
# clusterName: image: repository: sorintlab/stolon tag: v0.16.0-pg10 pullPolicy: IfNotPresent ## Add secrets manually via kubectl on kubernetes cluster and reference here # pullSecrets: # - name: "myKubernetesSecret" # used by create-cluster-job when store.backend is etcd etcdImage: repository: k8s.gcr.io/etcd-amd64 tag: 2.3.7 pullPolicy: IfNotPresent debug: false # Enable the creation of a shm volume shmVolume: enabled: false persistence: enabled: true ## If defined, storageClassName: <storageClass> ## If set to "-", storageClassName: "", which disables dynamic provisioning ## If undefined (the default) or set to null, no storageClassName spec is ## set, choosing the default provisioner. (gp2 on AWS, standard on ## GKE, AWS & OpenStack) ## storageClassName: "" accessModes: - ReadWriteOnce size: 10Gi rbac: create: true serviceAccount: create: true # The name of the ServiceAccount to use. If not set and create is true, a name is generated using the fullname template name: superuserSecret: name: "" usernameKey: pg_su_username passwordKey: pg_su_password replicationSecret: name: "" usernameKey: pg_repl_username passwordKey: pg_repl_password superuserPasswordFile: superuserUsername: "stolon" ## password for the superuser (REQUIRED if superuserSecret and superuserPasswordFile are not set) superuserPassword: replicationPasswordFile: replicationUsername: "repluser" ## password for the replication user (REQUIRED if replicationSecret and replicationPasswordFile are not set) replicationPassword: ## backend could be one of the following: consul, etcdv2, etcdv3 or kubernetes store: backend: kubernetes # endpoints: "http://stolon-consul:8500" kubeResourceKind: configmap pgParameters: {} # max_connections: "1000" ports: stolon: containerPort: 5432 metrics: containerPort: 8080 serviceMonitor: # When set to true then use a ServiceMonitor to collect metrics enabled: false # Custom labels to use in the ServiceMonitor to be matched with a specific Prometheus labels: {} # Set the namespace the ServiceMonitor should be deployed to # namespace: default # Set how frequently Prometheus should scrape # interval: 30s # Set timeout for scrape # scrapeTimeout: 10s job: autoCreateCluster: true autoUpdateClusterSpec: true annotations: {} clusterSpec: {} # sleepInterval: 1s # maxStandbys: 5 ## Enable support ssl into postgres, you must specify the certs. ## ref: https://www.postgresql.org/docs/10/ssl-tcp.html ## tls: enabled: false rootCa: |- serverCrt: |- serverKey: |- # existingSecret: name-of-existing-secret-to-postgresql keeper: uid_prefix: "keeper" replicaCount: 2 annotations: {} resources: {} priorityClassName: "" fsGroup: "" service: type: ClusterIP annotations: {} ports: keeper: port: 5432 targetPort: 5432 protocol: TCP nodeSelector: {} affinity: {} tolerations: [] volumes: [] volumeMounts: [] hooks: failKeeper: enabled: false podDisruptionBudget: # minAvailable: 1 # maxUnavailable: 1 extraEnv: [] # - name: STKEEPER_LOG_LEVEL # value: "info" proxy: replicaCount: 2 annotations: {} resources: {} priorityClassName: "" service: type: ClusterIP # loadBalancerIP: "" annotations: {} ports: proxy: port: 5432 targetPort: 5432 protocol: TCP nodeSelector: {} affinity: {} tolerations: [] podDisruptionBudget: # minAvailable: 1 # maxUnavailable: 1 extraEnv: [] # - name: STPROXY_LOG_LEVEL # value: "info" # - name: STPROXY_TCP_KEEPALIVE_COUNT # value: "0" # - name: STPROXY_TCP_KEEPALIVE_IDLE # value: "0" # - name: STPROXY_TCP_KEEPALIVE_INTERVAL # value: "0" sentinel: replicaCount: 2 annotations: {} resources: {} priorityClassName: "" nodeSelector: {} affinity: {} tolerations: [] podDisruptionBudget: # minAvailable: 1 # maxUnavailable: 1 extraEnv: [] # - name: STSENTINEL_LOG_LEVEL # value: "info" ## initdb scripts ## Specify dictionary of scripts to be run at first boot, the entry point script is create_script.sh ## i.e. you can use pgsql to run sql script on the cluster. ## # initdbScripts: # create_script.sh: | # #!/bin/sh # echo "Do something." ## nodePostStart scripts ## Specify dictionary of scripts to be run at first boot, the entry point script is postStartScript.sh ## i.e. you can create tablespace directory here. ## # nodePostStartScript: # postStartScript.sh: | # #!/bin/bash # echo "Do something."