thoughtbot / thoughtbot/flightdeck
Automatically terminate EC2 instances when the Kubelet stops reporting
Open
Nobody has claimed this yet.
aws
enhancement
- Dominant language
- HCL
- Stars
- 100
- Forks
- 11
- Avg merge
- 7h 37m
- Merged PRs (30d)
- 3
Description
We have seen several instances where:
- All pods on a node are marked as "Terminating"
- The underlying node reports that the Kubelet has stopped reporting
- EC2 healthchecks for the node are passing
We would like to deploy a mechanism to automatically detect and terminate these instances rather than doing it manually.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked “kubelet stopped posting node status” debugging guide and inspect the repository’s Terraform modules for the cluster and EC2 nodes. Define how kubelet silence is detected and how affected instances are safely terminated, then verify the mechanism handles the described terminating-pods scenario without relying on failing EC2 healthchecks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, terraform
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100