Skip to content
Discussion options

You must be logged in to vote

The 30-minute delay matches the documented default resync_period; the postponement itself is a safety
check, rather than evidence that topology spread constraints are unsupported.

In v2.0.3's reconciliation code,
Patroni configuration/restart errors prevent pending pod recreation when all pods are still running.
Your no route to host errors explain why that branch was taken. They do not establish whether the
underlying cause is CNI routing, a node firewall, NetworkPolicy, or another connectivity problem.

I would first verify that the operator pod's network context can reach each database pod on TCP 8008,
including both /config and /patroni, and compare a failing pod/node with a reachable …

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by TLINDEN
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants