Tink vs kube-apiserver
kube-apiserver authenticates, admits, and stores Kubernetes objects in etcd. That is not a mechanic. Tink installs in one command, watches the Linux server, explains what is wrong, and helps you fix it.
kube-apiserver serves the cluster API. Tink answers “why is this VPS sick?”
Accidental sysadmins land on kube-apiserver because every Kubernetes control-plane diagram starts there. Then the volume fills, nginx dies, and apiserver_request_total stays green — the VPS was never a Pod. A filling /var is a Tink warning; it is not a kube-apiserver job unless the API already stopped answering.
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-apiserver if you already operate Kubernetes and need an API. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | kube-apiserver |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — a control plane, kube-apiserver, scrape of :6443/metrics, and dashboards for request latency |
| What you get | Working monitoring, diagnosis, and approved fixes | A Kubernetes HTTP API. 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, etcd, Prometheus, Grafana, and the engineer who owns admission webhooks |
| Hidden costs | None — fully managed | TLS serving certs, etcd HA, webhook latency, 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-apiserver only serves objects already stored in etcd |
| Configuration | None after install — heuristics and AI | --secure-port, admission plugins, audit policy, and which apiserver_request_* series you actually graph |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | No — kube-apiserver serves request histograms. You still kubectl describe to learn why a Pod is stuck |
| Fix execution | Proposes and executes approved commands with an audit trail | API only — kube-apiserver cannot free disk, restart nginx, or rotate a host cert |
| Alerting | Built-in across 8 channels | None — Prometheus must scrape :6443/metrics 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 inflight requests. kube-apiserver does not predict host fill |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — kube-apiserver does not read host auth.log, journald, or host firewall state |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | A 6443 timeout is an API outage — only if Prometheus still runs and the control plane still answers |
| Public status page | Shareable URL with 90-day history | None — kube-apiserver has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — an apiserver_request_duration 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 :6443. No mechanic you text when /var filled on a VPS that is not in the cluster |
| Learning curve | None — works after install | Steep — Kubernetes, admission, etcd, Prometheus, PromQL, and which 5xx 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 an API server, not a sick-VPS mechanic |
When kube-apiserver is the right choice
Keep kube-apiserver when you already want that exact job:
- A Kubernetes API — you need authn, authz, admission, and etcd persistence, not a mechanic on a quiet VPS.
- An existing control plane — kube-apiserver, etcd, and the controllers already exist, and someone owns serving certs.
- Cluster-level questions — API 5xx, webhook latency, and inflight requests 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-apiserver”
kube-apiserver is in every Kubernetes control-plane diagram. A working ops loop for five Linux boxes is not:
- An apiserver_request_duration histogram still means you SSH in and change the box by hand
- Host fill, nginx, certs, and SSH brute-force never appear unless they already took the API down
- A filling /var is a Tink disk warning on every scan — kube-apiserver will stay quiet until :6443 already failed
- A single VPS with no cluster still needs a mechanic, not an admission plugin
For a 5-server team, Tink Mechanic at $45/month is cheaper than kube-apiserver plus the engineer who keeps Prometheus scrapes and etcd HA alive, and every scan includes a diagnosis a quiet :6443 /metrics dump will not type.
No API-server homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs kube-controller-manager · Tink vs kube-scheduler · Tink vs Prometheus