-
Notifications
You must be signed in to change notification settings - Fork 1k
Issues: zalando/postgres-operator
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
spec.users Role Creation Fails in v1.14.0 - myadmin Not Created with LOGIN
#2866
opened Feb 21, 2025 by
xtpclark
Inaccurate status-"RUNNING" shown when pod is stuck in pending state
bug
#2864
opened Feb 14, 2025 by
RavinaChidambaram
Postgres 1.14 logical operator default version is 1.13
question
#2859
opened Jan 29, 2025 by
arconsis-subash
Clarification on operator behaviour of backup to and cloning from S3
#2858
opened Jan 29, 2025 by
krauthex
Custom cluster port not working when i update my cluster
question
#2855
opened Jan 27, 2025 by
vhartmannselfee
Operator 1.14.0 and configAwsOrGcp.log_s3_bucket break cluster
#2852
opened Jan 23, 2025 by
baznikin
Ability to run the master and replica load-balancers from the same host
#2850
opened Jan 21, 2025 by
cowwoc
Unable to create timescaledb_toolkit extension using helm chart
#2848
opened Jan 21, 2025 by
odev-swe
Operator doesn't create prepared databases after standby replication from standalone source
#2846
opened Jan 17, 2025 by
klefevre
Pooler rollout update on 2 nodes is impossible with hard pod anti-affinity
#2843
opened Jan 17, 2025 by
murtll
logical-backup: a way to access gcs bucket using gke workload identity
#2836
opened Jan 8, 2025 by
ggramal
Does Kubernetes (1.30 version) support the Zalando operator v1.9.0?
question
#2813
opened Dec 9, 2024 by
Ajith61
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.