You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to set up crunchydata postgresql cluster, operator starts successfully but I am having troubles to set up the pg cluster.
I am using this version of operator 5.5.0 and this version of pg cluster 5.6.0
I have configured pgbackrest to backup on a local pvc but this seems to be causing an issue as following:
The configmap pgback-rest-config is not being created and this seems to be blocking the init container.
Has someone dealt with this issue previously, how can I solve this. Should the configmap normally be created when I deploy the cluster?
MountVolume.SetUp failed for volume "pgbackrest-config" : configmap "pgcluster-pgbackrest-config" not found
Warning FailedMount 2m39s (x58 over 118m) kubelet (combined from similar events): Unable to attach or mount volumes: unmounted volumes=[pgbackrest-config], unattached volumes=[pgbackrest-server cert-volume database-containerinfo kube-api-access-vxtxc patroni-config dshm postgres-data pgbackrest-config tmp]: timed out waiting for the condition
@kndoni Sorry you're having this issue. It's hard to say from the information you've provided so far, but I would start by looking in the operator's Pod logs to see if there are any errors detailing why the ConfigMap is not being created. One reason this might happen would be if you modified the RBAC so that the operator doesn't have the needed permissions, but there could certainly be other reasons. Hope this helps!
Hello team,
I am trying to set up crunchydata postgresql cluster, operator starts successfully but I am having troubles to set up the pg cluster.
I am using this version of operator 5.5.0 and this version of pg cluster 5.6.0
I have configured pgbackrest to backup on a local pvc but this seems to be causing an issue as following:
The configmap pgback-rest-config is not being created and this seems to be blocking the init container.
Has someone dealt with this issue previously, how can I solve this. Should the configmap normally be created when I deploy the cluster?
Statefulset content:
The text was updated successfully, but these errors were encountered: