Kubernetes (Homelab)

K8s basics, helm charts, storage classes, and small‑cluster ops for homelabs.

  • 10 Tracked terms
  • Last 30 days Feed window

What this topic collects on

An article joins this feed when it matches these terms. Each one is also a search of its own.

Latest in Kubernetes (Homelab)


dev.to > uhltak > k3s-statt-kubernetes-warum-die-rancher-distribution-unschlagbar-ist-5d0p

k3s statt Kubernetes: Warum die Rancher-Distribution unschlagbar ist

54+ min ago   (691+ words) Hier kommt k3s ins Spiel. Entwickelt von SUSE (bzw. Rancher), ist k3s keine abgespeckte Spielzeugversion, sondern eine hochkompakte, aber voll CVE-konforme Kubernetes-Distribution. Sie wurde speziell für IoT, Edge Computing und CI/CD-Pipelines konzipiert, hat sich aber längst auch als extrem robustes Fundament…...


dev.to > stark_zhuang_df5076f35c68 > 1551-elasticsearch-and-1462-memcached-endpoints-two-cache-layers-with-different-defaults-4eo6

1,551 Elasticsearch and 1,462 Memcached Endpoints: Two Cache Layers With Different Defaults

2+ hour, 35+ min ago   (836+ words) Two ZoomEye host searches collected on 18 September 2026 returned 1,551 observable services on port 9200 and 1,462 on port 11211. Port 9200 is Elasticsearch's HTTP interface. Port 11211 is Memcached's default listener. The counts are similar; the security stories are not. Elasticsearch: authentication that became a default…...


dev.to > kestre88 > backups-and-other-lies-266c

Backups and other lies

2+ hour, 55+ min ago   (177+ words) Every sysadmin I know has the same secret: we do not actually back up half the things we tell other people to back up. I have been doing this for a decade. My recovery codes live in a directory called…...


dev.to > stark_zhuang_df5076f35c68 > port-6443-in-the-wild-measuring-public-kubernetes-api-endpoint-exposure-3a89

Port 6443 in the Wild: Measuring Public Kubernetes API Endpoint Exposure

4+ hour, 18+ min ago   (526+ words) This article answers that question with a ZoomEye measurement and then separates what the number proves from what it does not. The measured result is an exposure count, not a vulnerability count. A host that answers on TCP port 6443 has…...


dev.to > lugerlogic > lab-notes-kubernetes-the-hard-way-for-real-this-time-step-07-4hna

[Lab Notes] Kubernetes the Hard Way, For Real This Time (Step 07)

5+ hour, 45+ min ago   (107+ words) Continuing my Kubernetes the Hard Way homelab build. Steps 01-06 are already done, this covers step 07. This step sets up the etcd cluster. From what I understand, etcd is basically Kubernetes' database, it's where the "state" of the whole cluster gets…...


dev.to > serverkueche > docker-volumes-vs-bind-mounts-where-your-data-really-lives-58h7

Docker volumes vs. bind mounts: where your data really lives

7+ hour, 5+ min ago   (762+ words) A container is ephemeral: delete it, and its data is gone. For your database, your Nextcloud files or your configuration to survive a docker compose down, you need volumes. This guide clears up the often confusing difference between named volumes…...


dev.to > serverkueche > keeping-your-whole-docker-stack-safely-up-to-date-4i8m

Keeping your whole Docker stack safely up to date

7+ hour, 5+ min ago   (1010+ words) A self-hosted stack is never "done". Container images get security updates, apps get new features –... Tagged with docker, selfhosted, devops....


dev.to > debasish87 > how-i-debugged-a-kv-cache-offloading-bug-in-vllm-52lj

How I Debugged a KV-Cache Offloading Bug in vLLM

8+ hour, 2+ min ago   (370+ words) LLM inference performance is often limited by GPU memory rather than raw compute. One of the problems I worked on in vLLM involved KV-cache offloading for models using mixed KV-cache groups. The failure was subtle: the existing logic assumed a…...


dev.to > technonotes > kubernetes-day-02-pidsignalsmount-3345

Kubernetes - Day - 02 - PID/Signals/Mount

10+ hour, 48+ min ago   (16+ words) Docker Pull the details from docker register. docker pull nginx Enter... Tagged with devops, docker, linux....


dev.to > sergey_shinder_ab2d943365 > our-cluster-had-kept-every-job-it-ever-finished-pd1

Our cluster had kept every job it ever finished

15+ hour, 24+ min ago   (794+ words) Deploys started failing on a Thursday morning. All of them, in every namespace, with the same message from our rollout tool: timed out waiting for pods. The pods were healthy and running. The cluster simply could not answer a question…...