Replies: 2 comments
-
I think I have figured out the issue, kube scheduler is just too busy:
why does operator try only 3 times? where can we increase that retry? |
Beta Was this translation helpful? Give feedback.
0 replies
-
@FxKu could please help me out here? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hej all
First of all, I have to say we are a happy user of the pg operator until recent upgrade it worked perfectly.
Ever since we have upgraded postgres-operator from 1.7.1 to 1.9.0 we are experiencing a funny issue.
Let say for every 10-deployment operator fails to create a database.
By that I mean that pvc where database should be created is empty.
We are using https://github.com/rancher/local-path-provisioner as the default storage class for our pg clusters.
Example of our reqeust to operator
Logs from the pg pod and operator:
keycloak-postgresql-0.log
postgres-operator-667568dcc9-vwxt8.log
When we did upgrade of the operator, we have also finally updated our k8s clusters from 1.23.x to 1.26.x
We are experiencing similar issue with postgres-operator 1.10.1.
Any idea what is the issue?
Beta Was this translation helpful? Give feedback.
All reactions