Repeated abrupt termination in EKS, v28.0 due to bad DNS
Shows how to fix repeated abrupt termination in EKS, v28.0 due to bad DNS. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
[kishorenc (maintainer)]: The fix for ignoring bad DNS resolution is part of the v29.0 GA release. If Typesense pods crash abruptly on EKS with "Not connected" replication errors, upgrade to v29.0.
Steps
- [kishorenc (maintainer)]: The fix for ignoring bad DNS resolution is part of the v29.0 GA release.
- If Typesense pods crash abruptly on EKS with "Not connected" replication errors, upgrade to v29.0.
When to use
Use this skill when you run into "Repeated abrupt termination in EKS, v28.0 due to bad DNS".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: new v28.0, 10.10.13, v29.0. If you are on something much newer or older, the details may have shifted.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.