Tink vs cluster-autoscaler
cluster-autoscaler is a Kubernetes controller. It watches pending pods and underused Nodes, then grows or shrinks a cloud node group. That is not a mechanic. Tink installs in one command, watches the Linux server, explains what is wrong, and helps you fix it.
CA scales node groups. Tink answers “why is this VPS sick?”
Accidental sysadmins land on cluster-autoscaler because every Kubernetes capacity diagram mentions it. Then the volume fills, nginx dies, and the node group stays the same size — the VPS was never a Node. A filling /var is a Tink warning; it is not an unschedulable pod unless you already run CA on that cluster.
Tink is the other job: detect the issue on the machine, say why it happened in plain English, propose the command, and run it only after you approve. Keep cluster-autoscaler if you already operate Kubernetes and need node-group scaling. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | cluster-autoscaler |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — a cluster, IAM, node groups, cluster-autoscaler, and still no host mechanic until Prometheus and a scale policy exist |
| What you get | Working monitoring, diagnosis, and approved fixes | More or fewer Nodes. The box that already exists is still yours to diagnose and SSH |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Free software (Apache 2.0). You still pay for Kubernetes, cloud nodes, and the engineer who owns scale-down taints |
| Hidden costs | None — fully managed | Unschedulable-pod loops, expander choice, scale-down delays, and a second tool that pages you when /var fills |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | None on the OS — cluster-autoscaler only watches pending pods and node-group capacity |
| Configuration | None after install — heuristics and AI | expander, scan-interval, scale-down-unneeded-time, and which node groups CA is allowed to mutate |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | No — cluster-autoscaler logs scale-up. You still SSH or kubectl describe to learn why a VPS is sick |
| Fix execution | Proposes and executes approved commands with an audit trail | Scale only — cluster-autoscaler cannot free disk, restart nginx, or rotate a cert on a VPS |
| Alerting | Built-in across 8 channels | None — scrape :8085 or watch node-group size before anyone is paged about the host |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Never — CA adds a Node after pods already failed to schedule. It does not forecast host fill |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — cluster-autoscaler does not read auth.log, journald SSH, or host firewall state |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | A silent CA is a missing Deployment — only if the API server still answers |
| Public status page | Shareable URL with 90-day history | None — cluster-autoscaler has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a scale-up event is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire node-group metrics into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | kubectl get nodes. No mechanic you text when /var filled on a VPS that is not a Node |
| Learning curve | None — works after install | Steep — Kubernetes, IAM, expanders, scale-down, and which pending pod actually means you needed another VM |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run Kubernetes and need node-group scaling, not a sick-VPS mechanic |
When cluster-autoscaler is the right choice
Keep cluster-autoscaler when you already want that exact job:
- Node groups — CA is how Kubernetes adds a VM when pods will not schedule. You need it to grow capacity, not to watch a quiet VPS.
- An existing cluster — IAM, node groups, and a scale-down policy already exist, and someone owns expander flags.
- Capacity questions — pending pods and underused Nodes matter more than host nginx, certs, and SSH.
- Hosts that only exist as Nodes — you already run Kubernetes, not a sick-box SSH loop.
The real cost of “just run cluster-autoscaler”
cluster-autoscaler is in every Kubernetes capacity diagram. A working ops loop for five Linux boxes is not:
- A scale-up event still means you SSH in and change the box by hand
- Host fill, nginx, certs, and SSH brute-force never appear unless they show up as pending pods you already have
- A filling /var is a Tink disk warning on every scan — CA will stay quiet until pods already failed to schedule
- A single VPS with no cluster still needs a mechanic, not a node-group controller
For a 5-server team, Tink Mechanic at $45/month is cheaper than cluster-autoscaler plus the engineer who keeps expanders and scale-down taints alive, and every scan includes a diagnosis a quiet node-group size will not type.
No node-group homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs kubelet · Tink vs kube-controller-manager · Tink vs Prometheus