Ty Van

Live site: gaming.tyvan.dev Why I Built This I read gaming news more often than I should probably admit in a professional setting. The problem is not that there is no gaming news. The problem is the opposite. There is too much of it, scattered across different publishers, feeds, launchers, communities, and whatever tab I opened three days ago and now refuse to close because “I might need it later”. So I wanted a small web app with one job: show latest gaming articles keep them easy to scan preserve the original publisher links avoid turning the homepage into a casino lobby with CSS That became Gaming Feed, a simple Next.js app backed by an existing PostgreSQL table of RSS-style articles. ...

Why I Wanted Dozzle I maintain a small k0s Kubernetes cluster for my personal services. kubectl logs works fine, but after a while it becomes tiring to keep jumping between namespaces, deployments, replicas, and pod names. I wanted a lightweight web UI where I could open one page, search for a workload, and read logs without turning every debugging session into a command-line treasure hunt. Dozzle looked like a good fit because it can run directly in Kubernetes mode. That means I did not need to mount the Docker socket or run a node-level log agent. The goal was simple: view pod logs from the cluster keep access read-only expose it through the Traefik ingress controller I already had route traffic through my existing Cloudflare Tunnel protect it with authentication ...

How I deployed a private Netdata dashboard on my personal k0s cluster using Helm, static local storage, Traefik, and Cloudflare Access.

A practical CI/CD setup for building a Next.js app, publishing a container image, and deploying it to a k0s Kubernetes cluster through GitHub Actions.

Intro As previous post we’re already setup k0s as Kubernates Cluster