Before this PR:
For the sake of simplicity we'd refer to localhost when setting up the distributed timelock cluster on Antithesis setup. I have a suspicion that could explain some of the problems we're seeing with our setup (like some nodes never being able to finish SSL handshakes, others reporting Remote potential leader is claiming to be you!, etc...)
After this PR:
==COMMIT_MSG==
We now just render the desired hostname for each of the timelock containers on the Antithesis simulation
==COMMIT_MSG==
Priority:
Concerns / possible downsides (what feedback would you like?):
svc-autorelease
commented
3 months ago
General
Before this PR: For the sake of simplicity we'd refer to localhost when setting up the distributed timelock cluster on Antithesis setup. I have a suspicion that could explain some of the problems we're seeing with our setup (like some nodes never being able to finish SSL handshakes, others reporting
Remote potential leader is claiming to be you!, etc...)After this PR:
==COMMIT_MSG== We now just render the desired hostname for each of the timelock containers on the Antithesis simulation ==COMMIT_MSG==
Priority:
Concerns / possible downsides (what feedback would you like?):
Is documentation needed?: