weblogtag
k0s
14 posts with this tag, newest first.
Tags, archive, series1 active
Tags
Archive
More
Posts 14
-
One Evening, Three Problems: Mail Down, Memory Full, Wrong Docker Arch
Incident log from a 4GB single-node k0s box: snappymail OOMKilled loop, 163% memory overcommit, swap thrashing disguised as disk I/O, and a docker buildx arch mismatch.
-
Traefik → APISIX on a single node: what broke during the ingress migration
A direct cutover from Traefik to APISIX on bare-metal k0s: hostNetwork port conflicts, a broken --set with commas, an addPrefix bug causing 404s on assets, and eight more findings.
-
Full observability on one VPS: metrics, logs, alerts, dashboards — 452 MiB requested
How VictoriaMetrics, VictoriaLogs, Promtail, vmalert, and Grafana fit together on a 2-core VPS: architecture, the full resource bill, and repeating patterns.
-
VictoriaLogs on k0s: a log database that fits in 128 MiB
Single-pod VictoriaLogs: 90 lines of YAML, Recreate strategy for hostPath storage, Loki-compatible ingestion, LogsQL basics, and Grafana datasource pitfalls.
-
vmsingle: one VictoriaMetrics binary instead of the whole Prometheus stack
VictoriaMetrics single-node on k0s: embedded scraper with static targets, cAdvisor RBAC, hostPath PV, and a stable ClusterIP to survive CoreDNS restarts.
-
How this site is built
FastAPI, k0s, Traefik, WireGuard, and plain Markdown — a tour of the infrastructure behind this personal site.
-
Rotating Tor HTTP proxy in Kubernetes
Running zhaow-de/rotating-tor-http-proxy in k0s: N Privoxy+Tor circuits, HAProxy round-robin, stats UI on NodePort 30444.
-
Beszel: lightweight server monitoring with Telegram alerts
A Go binary that fits in 50 MiB and sends Telegram alerts when the server goes down. Why not Grafana.
-
IKEv2 and WireGuard running in separate Kubernetes namespaces
Why VPN pods run inside k0s with hostNetwork and privileged mode, and the tradeoffs that come with it.
-
Deploying to k0s with a shell script instead of CI/CD
One shell script, a self-hosted Docker registry, and envsubst. No GitHub Actions, no ArgoCD — here's why that's enough.
-
Self-hosted Docker registry inside the k0s cluster
registry:2 on NodePort 30500, no external dependencies for deploys, and automatic cleanup of old image tags.
-
Automatic TLS with cert-manager, Let's Encrypt, and Traefik IngressRoutes
ClusterIssuers, HTTP-01 challenges, multi-SAN certificates, and addPrefix middleware for subdomain routing.
-
Helm charts declared in k0s config: Flannel, Traefik, cert-manager, Prometheus
k0s has a built-in Helm controller. Declare charts in k0s.yaml and they install automatically on startup — no FluxCD required.
-
Setting up a Debian VPS for k0s: sysctl, kernel modules, and the install
What 01-prepare-vm.sh actually does: disabling swap, tuning inotify limits, loading kernel modules, and installing k0s single-node.
No posts match the selected filters.