Skip to content

Conversation

@Hades32
Copy link
Contributor

@Hades32 Hades32 commented Sep 21, 2023

With these changes (and the update to v0.25) this setup should finally reliably work.

  • The reset-peers flag is needed to recover from pod IP changes
  • read/write-lag flags are made explicit as, depending on cluster topology, folks will want different values here
  • a readiness probe fixes consumers hitting dead nodes and causing even more issues
  • the publishNotReadyAddresses setting ensures that pod IPs are still available for clustering

@wille
Copy link

wille commented Nov 1, 2023

Thanks,
I also had to set

          args:
            - --peering-address
            - $(POD_IP)
          env:
            - name: POD_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP

@IT-Guy007
Copy link

Also update the readme if approved, the config works for me on Google Cloud.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants