Channel
@KubeBuilders
On this record: Topic · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
1,626subscribers
+24 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001371689501 |
|---|---|
| Type | Channel |
| Username | @KubeBuilders |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 2 times, most recently 7 October 2026 |
| On Telegram | t.me/KubeBuilders |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
This channel’s posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 10:41 | 1,626 | +3 |
| 16 Sept 2026, 16:56 | 1,623 | +2 |
| 9 Sept 2026, 11:17 | 1,621 | +4 |
| 4 Sept 2026, 07:55 | 1,617 | +1 |
| 31 Aug 2026, 13:43 | 1,616 | -5 |
| 28 Aug 2026, 06:38 | 1,621 | +5 |
| 25 Aug 2026, 01:07 | 1,616 | +6 |
| 15 Aug 2026, 00:47 | 1,610 | +6 |
| 11 Aug 2026, 12:28 | 1,604 | +1 |
| 8 Aug 2026, 08:32 | 1,603 | +1 |
| 7 Aug 2026, 16:48 | 1,602 | no change |
| 7 Aug 2026, 14:02 | 1,602 | first reading |
20 posts held, back to 28 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 9 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
MAAS (Metal-as-a-Service) is a production-grade tool that automates provisioning, network config, and OS installs (Ubuntu, CentOS, Windows, ESXi) across physical servers using PXE, IPAM, and full API-driven workflows. More: https://ku.bz/9z6rg3_cZ
When one pull request spans app code, config, and CI, the weakest point is usually not the app. Artem Lajko explains that ownership is split between developers and platform teams, so config changes lack true end-to-end accountability. That makes breakage harder to spot before merge and easier to discover only when CI or infrastructure behavior changes.
This article explains how Kubernetes pod DNS failures can come from the default ndots:5 setting and a Linux conntrack issue, and shows how ndots:2 plus single-request-reopen can reduce DNS noise and fix intermittent resolution errors. More: https://ku.bz/pZG7kVlFk
K8up is a Kubernetes Operator that helps you: - Backup all PVCs marked as ReadWriteMany or with a specific label. - Perform individual, on-demand backups. - Schedule backups to be executed regularly. And more. More: https://ku.bz/1ynMNZrK9
This week on Learn Kubernetes Weekly 195: 🔍 Practical Detection Engineering for Kubernetes: Baselining Audit Logs 🤖 Building an AI Agent That Runs Your SRE Operations — What I Learned, What Works, and How You Can Do It Too 🛡️ Building an OSS Kubernetes Security Console 🧩 User Namespaces in Kubernetes: The Implementation 🔀 Vlan Migration: Moving a Live Kubernetes Cluster Without Downtime Read it now: https://kube.to…
This tutorial teaches how to build a production-like Kubernetes cluster on bare metal using Hyper-V VMs with MetalLB, Ingress NGINX, Longhorn storage, and HPA. More: https://ku.bz/lgLkmqb-9
The newest tool is not automatically the right architectural choice. Before evaluating implementations, Fabián Sellés Rosa defined three criteria: flexibility, production maturity, and operational effort. This made it possible to compare Crossplane, a custom controller, and KRO with ACK on the same terms. You will learn: - Why KIAM became urgent to replace after years of stable operation - How to define evaluation…
Jordan Karapanagiotis was running AI inference on edge devices with a monolithic Docker container — no visibility into app state, no control over individual services. Then the team discovered K3s at KubeCon. They split their codebase into proper microservices, deployed on a single-node K3s cluster, and haven't looked back. Three years in, debugging is straightforward: check the logs, find the service, trace the root…
Scientific workloads require specialized tools for ML, interactive access, and advanced scheduling. Ricardo Rocha shares how CERN is tracking tools like Kubeflow and KServe for ML workloads, Container SSH for interactive access, and Kueue for cross-cluster scheduling. Watch the full interview: https://ku.bz/BCzSD9bF_
Kubeswitch is a command-line tool to ease switching between different kubectl contexts. Kubeswitch is a drop-in replacement for kubectx. More: https://ku.bz/Jj30sYB-L
Reloader is a Kubernetes controller that monitors changes in ConfigMap and Secrets and triggers rolling upgrades on Pods with their associated Deployment, StatefulSet or DaemonSet. More: https://ku.bz/NBWH644n8
This tutorial shows how to automatically create and scale GitHub Actions runners on Kubernetes using Argo CD ApplicationSets that read config files from Git and deploy runner pods with custom resources and autoscaling. More: https://ku.bz/0h2gRcqLb
Showing the 12 most recent of 20 posts we hold for @KubeBuilders. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 1 October 2026 — this entry's latest reading, not the date you are reading this.
“Kube Builders” (@KubeBuilders), 1,626 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/KubeBuilders.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.