Tink vs kube-controller-manager
kube-controller-manager loops controllers against the API until Deployments, Nodes, and Endpoints match desired state. That is not a mechanic. Tink installs in one command, watches the Linux server, explains what is wrong, and helps you fix it.
kube-controller-manager reconciles objects. Tink answers “why is this VPS sick?”
Accidental sysadmins land on kube-controller-manager because every Kubernetes control-plane diagram includes it. Then the volume fills, nginx dies, and the controllers stay green — the VPS was never a ReplicaSet. A filling /var is a Tink warning; it is not a kube-controller-manager job unless a Node already flipped NotReady.
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 kube-controller-manager if you already operate Kubernetes and need object reconcile. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | kube-controller-manager |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — a control plane, kube-controller-manager, scrape of :10257, and dashboards for workqueue depth |
| What you get | Working monitoring, diagnosis, and approved fixes | Reconcile loops. 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 the controllers |
| Hidden costs | None — fully managed | Control-plane HA, leader election, metric cardinality, and a second tool that actually watches the Linux host |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | None on the OS — kube-controller-manager only reconciles objects the API already stored |
| Configuration | None after install — heuristics and AI | controllers, --controllers flags, leader election, and which workqueue_adds series you actually graph |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | No — kube-controller-manager serves workqueues. You still kubectl describe to learn why a ReplicaSet is stuck |
| Fix execution | Proposes and executes approved commands with an audit trail | Reconcile only — kube-controller-manager cannot free disk, restart nginx, or rotate a cert |
| Alerting | Built-in across 8 channels | None — Prometheus must scrape it 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 workqueue gauges. kube-controller-manager does not predict host fill |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — kube-controller-manager does not read auth.log, journald, or host firewall state |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | A NotReady node is a Node object — only if the API server still answers and Prometheus still scrapes |
| Public status page | Shareable URL with 90-day history | None — kube-controller-manager has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a workqueue_depth dump 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 :10257. No mechanic you text when /var filled on a VPS that is not in the cluster |
| Learning curve | None — works after install | Steep — Kubernetes, controller flags, Prometheus, PromQL, and which reconcile failures actually mean the box is sick |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run Kubernetes and need object reconcile, not a sick-VPS mechanic |
When kube-controller-manager is the right choice
Keep kube-controller-manager when you already want that exact job:
- Object reconcile — you need ReplicaSets, Endpoints, and Node status looped, not a mechanic on a quiet VPS.
- An existing control plane — kube-controller-manager, etcd, and the API server already exist, and someone owns controller flags.
- Cluster-level questions — NotReady nodes, replica counts, and endpoint slices 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 kube-controller-manager”
kube-controller-manager is in every Kubernetes control-plane diagram. A working ops loop for five Linux boxes is not:
- A workqueue_depth gauge still means you SSH in and change the box by hand
- Host fill, nginx, certs, and SSH brute-force never appear unless they already flipped a Node NotReady
- A filling /var is a Tink disk warning on every scan — kube-controller-manager will stay quiet until a controller already failed to reconcile
- A single VPS with no cluster still needs a mechanic, not a controller flag
For a 5-server team, Tink Mechanic at $45/month is cheaper than kube-controller-manager plus the engineer who keeps Prometheus scrapes and control-plane HA alive, and every scan includes a diagnosis a quiet :10257 /metrics dump will not type.
No controller homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs kube-scheduler · Tink vs kube-proxy · Tink vs Prometheus