Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: make crunchy easy to enable #2061

Open
DerekRoberts opened this issue Aug 22, 2024 · 1 comment
Open

feat: make crunchy easy to enable #2061

DerekRoberts opened this issue Aug 22, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@DerekRoberts
Copy link
Member

We have a line in the Helm values file. Tie in better so that one line can enable Crunchy.

crunchy: # enable it for TEST and PROD, for PR based pipelines simply use single postgres
enabled: false
crunchyImage: artifacts.developer.gov.bc.ca/bcgov-docker-local/crunchy-postgres-gis:ubi8-15.2-3.3-0
postgresVersion: 15
postGISVersion: '3.3'
imagePullPolicy: Always
instances:
name: ha # high availability
replicas: 1 # 2 or 3 for high availability in TEST and PROD.
metadata:
annotations:
prometheus.io/scrape: 'true'
prometheus.io/port: '9187'
dataVolumeClaimSpec:
storage: 120Mi
storageClassName: netapp-block-standard
requests:
cpu: 25m
memory: 256Mi
limits:
cpu: 100m
memory: 512Mi
replicaCertCopy:
requests:
cpu: 1m
memory: 32Mi
limits:
cpu: 50m
memory: 64Mi
pgBackRest:
enabled: false
image: # it's not necessary to specify an image as the images specified in the Crunchy Postgres Operator will be pulled by default
retention: "1" # Ideally a larger number such as 30 backups/days
# If retention-full-type set to 'count' then the oldest backups will expire when the number of backups reach the number defined in retention
# If retention-full-type set to 'time' then the number defined in retention will take that many days worth of full backups before expiration
retentionFullType: count
repos:
schedules:
full: 0 8 * * *
incremental: 0 0,4,12,16,20 * * *
volume:
accessModes: "ReadWriteOnce"
storage: 64Mi
storageClassName: netapp-file-backup
repoHost:
requests:
cpu: 1m
memory: 64Mi
limits:
cpu: 50m
memory: 128Mi
sidecars:
requests:
cpu: 1m
memory: 64Mi
limits:
cpu: 50m
memory: 128Mi
patroni:
postgresql:
pg_hba: "host all all 0.0.0.0/0 md5"
parameters:
shared_buffers: 16MB # default is 128MB; a good tuned default for shared_buffers is 25% of the memory allocated to the pod
wal_buffers: "64kB" # this can be set to -1 to automatically set as 1/32 of shared_buffers or 64kB, whichever is larger
min_wal_size: 32MB
max_wal_size: 64MB # default is 1GB
max_slot_wal_keep_size: 128MB # default is -1, allowing unlimited wal growth when replicas fall behind
proxy:
pgBouncer:
image: # it's not necessary to specify an image as the images specified in the Crunchy Postgres Operator will be pulled by default
replicas: 1
requests:
cpu: 1m
memory: 64Mi
limits:
cpu: 50m
memory: 128Mi
# Postgres Cluster resource values:
pgmonitor:
enabled: false
exporter:
image: # it's not necessary to specify an image as the images specified in the Crunchy Postgres Operator will be pulled by default
requests:
cpu: 1m
memory: 64Mi
limits:
cpu: 50m
memory: 128Mi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant