Tink vs kubelet
kubelet is the Kubernetes node agent. It runs pods and exposes /metrics and /metrics/cadvisor so Prometheus can scrape the Node. That is not a mechanic. Tink installs in one command, watches the Linux server, explains what is wrong, and helps you fix it.
kubelet runs the node. Tink answers “why is this VPS sick?”
Accidental sysadmins land on kubelet metrics because every kube-prometheus diagram scrapes them. Then the volume fills, nginx dies, and the node gauges stay green — the VPS was never a Node. A filling /var is a Tink warning; it is not a kubelet sample unless you already run Kubernetes on that box.
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 kubelet if you already operate Kubernetes and need pods to run. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | kubelet |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — a cluster, kubelet TLS, a scrape job, and still no alerts until Prometheus and Alertmanager exist |
| What you get | Working monitoring, diagnosis, and approved fixes | The node agent plus raw /metrics. The box 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, Prometheus, Grafana, and the engineer who owns kubelet auth |
| Hidden costs | None — fully managed | TLS, bearer tokens, cadvisor cardinality, and a second tool that actually pages you when /var fills |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Node runtime metrics — kubelet is how pods run, not a host mechanic |
| Configuration | None after install — heuristics and AI | kubelet flags, authentication, cadvisor, and which /metrics* endpoint Prometheus is allowed to hit |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | No — kubelet_running_pods is a gauge. You still SSH or kubectl describe to learn why |
| Fix execution | Proposes and executes approved commands with an audit trail | Metrics only — kubelet cannot free disk, restart nginx, or rotate a cert on a VPS |
| Alerting | Built-in across 8 channels | None — Prometheus must scrape kubelet and a PromQL rule must fire before anyone is paged |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Only if you already wrote a PromQL forecast on node series. kubelet does not predict |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — kubelet does not read auth.log, journald, or host firewall state |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | A silent kubelet is a Node NotReady — only if the API server still answers and Prometheus still scrapes |
| Public status page | Shareable URL with 90-day history | None — kubelet has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a kubelet_node_name scrape is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire Prometheus into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | /metrics on the kubelet port. No mechanic you text when /var filled on a VPS that is not a Node |
| Learning curve | None — works after install | Steep — Kubernetes, kubelet auth, cadvisor, Prometheus, and which node series actually mean the box is sick |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run Kubernetes and need node runtime metrics, not a sick-VPS mechanic |
When kubelet is the right choice
Keep kubelet when you already want that exact job:
- Running pods — kubelet is the node agent. You need it to schedule containers, not to watch a quiet VPS.
- An existing kube-prometheus stack — TLS, scrape, and Grafana already exist, and someone owns cadvisor cardinality.
- Node-level questions — pod density, cgroup usage, and NotReady 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 scrape kubelet”
kubelet metrics are in every Kubernetes monitoring diagram. A working ops loop for five Linux boxes is not:
- A kubelet_running_pods gauge 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 node series Prometheus already scraped
- A filling /var is a Tink disk warning on every scan — kubelet will stay quiet unless you already wired PromQL
- A single VPS with no cluster still needs a mechanic, not a kubelet scrape job
For a 5-server team, Tink Mechanic at $45/month is cheaper than kubelet plus the engineer who keeps Prometheus scrapes and TLS auth alive, and every scan includes a diagnosis a quiet /metrics dump will not type.
No kubelet TLS homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs kube-state-metrics · Tink vs cAdvisor · Tink vs Prometheus