How We Set Up One Private Container Registry for 6 AKS Clusters Across 3 Regions and What Broke Along the Way This post walks through how we architected a single private container registry accessible by all six of our AKS clusters across three Azure regions. I'll cover what worked, what silently failed for weeks before we noticed, and the decisions I'd make differently today. https://dev.to/alex_coder19283/how-we-s…

Channel
DevOps&SRE Library
@devopslibrary
On this record: Topic · Growth · Engagement · What this channel posts · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
19,856subscribers
+186 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001329220738 |
|---|---|
| Type | Channel |
| Username | @devopslibrary |
| Created | 21 April 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/devopslibrary |
Topic
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 15:01 | 19,856 | +7 |
| 16 Sept 2026, 08:21 | 19,849 | +12 |
| 14 Sept 2026, 16:58 | 19,837 | +5 |
| 13 Sept 2026, 01:19 | 19,832 | +11 |
| 10 Sept 2026, 23:41 | 19,821 | +11 |
| 7 Sept 2026, 21:59 | 19,810 | +20 |
| 5 Sept 2026, 00:16 | 19,790 | +15 |
| 3 Sept 2026, 06:27 | 19,775 | +2 |
| 2 Sept 2026, 00:39 | 19,773 | +6 |
| 31 Aug 2026, 23:18 | 19,767 | +9 |
| 31 Aug 2026, 01:04 | 19,758 | +2 |
| 30 Aug 2026, 00:24 | 19,756 | -4 |
| 29 Aug 2026, 03:26 | 19,760 | +6 |
| 28 Aug 2026, 04:58 | 19,754 | +7 |
| 26 Aug 2026, 06:48 | 19,747 | -3 |
| 25 Aug 2026, 04:43 | 19,750 | -2 |
| 24 Aug 2026, 03:14 | 19,752 | -5 |
| 22 Aug 2026, 08:06 | 19,757 | +5 |
| 20 Aug 2026, 19:42 | 19,752 | +10 |
| 19 Aug 2026, 22:05 | 19,742 | first reading |
Engagement
89 posts held, back to 29 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 57 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 9.10%
- avg views ÷ 19,856 subscribers
- Avg views / post
- 1,810
- 12 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 12
- of 89 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 89 (29 July 2026 – 2 September 2026) |
| Views total | 21,682 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 01:00 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Video runtime
- 1m 59s
- Average length
- 1m 59s
Measured directly from 1 video 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.
Advertising
- Ad load
- 15.7%
- 14 of 89 posts carry an ad marker
- Regulatory tokens
- 14
- posts carrying an erid · 14 distinct tokens
- Median views · ads
- 2,630
- over 14 measured posts
- Median views · rest
- 2,530
- over 75 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VtzquZctk3 | 1 | 10 August 2026 | 10 August 2026 |
| 2VtzqvERRyd | 1 | 25 August 2026 | 25 August 2026 |
| 2VtzqvHEFpX | 1 | 11 August 2026 | 11 August 2026 |
| 2VtzqvY8GGz | 1 | 29 July 2026 | 29 July 2026 |
| 2VtzqvYKd9d | 1 | 17 August 2026 | 17 August 2026 |
| 2VtzqvfVsqU | 1 | 3 August 2026 | 3 August 2026 |
| 2Vtzqvqgags | 1 | 12 August 2026 | 12 August 2026 |
| 2VtzqvwpkP4 | 1 | 6 August 2026 | 6 August 2026 |
| 2VtzqwWeuAs | 1 | 1 September 2026 | 1 September 2026 |
| 2VtzqwcGyWj | 1 | 19 August 2026 | 19 August 2026 |
| 2VtzqwyJGNX | 1 | 26 August 2026 | 26 August 2026 |
| 2VtzqxCannf | 1 | 20 August 2026 | 20 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it. 2 further tokens are held for this entry and not listed here.
Measured over the 89 most recent posts we hold, published 29 July 2026 to 2 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
We Tested Copy Fail in Kubernetes: PSS Restricted and RuntimeDefault Did Not Block AF_ALG On April 22, 2026, the Linux CNA published CVE-2026-31431, a Linux kernel vulnerability in algif_aead, the AEAD side of the kernel's AF_ALG crypto socket interface. Xint named the bug Copy Fail and showed how page-cache bytes for a read-only file can be changed without dirtying the file on disk. https://juliet.sh/blog/we-teste…
Для тех, кто работает с Kubernetes и облачной инфраструктурой, в октябре намечается отличный повод выбраться из рабочих чатов и встретиться офлайн 👀 Что будем обсуждать: – AI и облачную инфраструктуру; – экономику платформ и безопасность в эпоху LLM; – эксплуатацию Kubernetes и observability; – сети и Service Mesh; – железо, ЦОДы и bare-metal-инфраструктуру. В течение дня вас ждут доклады, общение с коллегами и акт…
The GPU Bill Was $40,000. Nobody Knew Why. Finance had flagged the AWS bill. GPU spend for the past 30 days: $40,200. The budget was $18,000. Nobody on the call could explain where the extra $22,000 had gone. https://medium.com/@mateenanjum/the-gpu-bill-was-40-000-nobody-knew-why-e6e953b25f4a
We're a 3-person tech team running production Kubernetes — So we built an AI SRE We needed help. Not a dashboard. Not another alerting rule. An actual pair of hands that could look at an alert, check if it's real, figure out what's wrong, and either fix it or tell us where to look. https://medium.com/@leo_62530/were-a-3-person-tech-team-running-production-kubernetes-so-we-built-an-ai-sre-61ee28810448
GitHub Runners: Scaling ARC with Argo CD ApplicationSets But managing multiple self-hosted runners manually can be tedious, especially in a Kubernetes environment. In this article, I'll show how I automated this process using Argo CD ApplicationSet, making my GitHub runners dynamic, declarative, and scalable. https://medium.com/@nahuel.aldrey/github-runners-scaling-arc-with-argo-cd-applicationsets-5d660bee0ef4
Kubernetes AuthN the Hard Way We're wiring together three components: OpenLDAP (your user directory), Dex (the authentication translator), and the Kubernetes API Server (the skeptical consumer of identity tokens). Every bug, every misconfiguration, and every "why is this not working" moment is documented here because I hit all of them personally. https://medium.com/@jinalpatel11121999/kubernetes-authn-the-hard-way-…
nodes/proxy GET: One Kubernetes permission too many The nodes/proxy GET RBAC permission allows any ServiceAccount to execute code inside any Pod in the cluster, without leaving a single trace in the audit logs. This article details the issue, how to check if you are vulnerable, the fixes to apply, and the preventive measures you can put in place if you can't patch right away. https://blog.zwindler.fr/en/2026/05/19/…
VLAN Migration: Moving a Live Kubernetes Cluster Without Downtime I migrated the entire k3s cluster from a flat network to a proper VLAN architecture: Server VLAN 20 for k3s nodes and services, Storage VLAN 30 for the NAS, and the existing default VLAN 1 for clients. This involved changing IPs on all VMs, updating MetalLB, reconfiguring Traefik, and recovering from an etcd quorum loss when I moved too many nodes at …
User Namespaces in Kubernetes Part I: All You Need to Know https://blog.sdfg.com.ar/posts/userns-in-kubernetes-part-i Part II: Mappings and File Ownership https://blog.sdfg.com.ar/posts/userns-in-kubernetes-part-ii Part III: The Implementation https://blog.sdfg.com.ar/posts/userns-in-kubernetes-part-iii
Building an OSS Kubernetes Security Console with MCP That is what this series is about: building an open source Kubernetes security console that collects posture, vulnerability, policy, and runtime signals, exposes them through Kubernetes-native objects where possible, and wires that data into an MCP server so an AI agent can help triage across the whole stack. https://cloudsecburrito.com/building-an-oss-kubernetes…
Building an AI Agent That Runs Your SRE Operations — What I Learned, What Works, and How You Can Do It Too Not a smarter alert. Not a better dashboard. An actual reasoning system — one that reads Splunk, queries AppDynamics, checks the Kubernetes pods, searches the Confluence runbooks, looks at what GitLab deployed recently, and comes back with a diagnosis and a proposed action. https://blog.stackademic.com/buildin…
Showing the 12 most recent of 89 posts we hold for @devopslibrary. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Appears in Telegram’s recommendations for other channels
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.
@devops_jobs_feed · 21,917
Telegram ranks this channel #14 of 95 here — alongside 94 others — read 22 September 2026
@DevOPSitsec · 23,684
Telegram ranks this channel #15 of 90 here — alongside 89 others — read 18 September 2026
@devopsforlove · 44,673
Telegram ranks this channel #16 of 95 here — alongside 94 others — read 9 September 2026
@devopsina · 23,617
Telegram ranks this channel #27 of 90 here — alongside 89 others — read 18 September 2026
@hahacker_news · 25,571
Telegram ranks this channel #31 of 59 here — alongside 58 others — read 14 September 2026
@srv_admin · 32,572
Telegram ranks this channel #35 of 96 here — alongside 95 others — read 5 September 2026
@abhishekveeramalla · 50,872
Telegram ranks this channel #37 of 68 here — alongside 67 others — read 25 August 2026
@bzd_channel · 36,402
Telegram ranks this channel #44 of 57 here — alongside 56 others — read 1 September 2026
@ITSTAND_ORG · 155,546
Telegram ranks this channel #45 of 98 here — alongside 97 others — read 9 September 2026
@bashdays · 23,634
Telegram ranks this channel #46 of 94 here — alongside 93 others — read 18 September 2026
@yandexcloudnews · 21,888
Telegram ranks this channel #56 of 97 here — alongside 96 others — read 22 September 2026
@rebrain_devops · 28,873
Telegram ranks this channel #56 of 94 here — alongside 93 others — read 9 September 2026
@i_odmin · 26,669
Telegram ranks this channel #62 of 89 here — alongside 88 others — read 12 September 2026
@github_repos · 27,297
Telegram ranks this channel #66 of 76 here — alongside 75 others — read 11 September 2026
@goproglib · 24,076
Telegram ranks this channel #76 of 91 here — alongside 90 others — read 17 September 2026
@linuxgram · 72,668
Telegram ranks this channel #76 of 90 here — alongside 89 others — read 19 August 2026
This channel appears in 16 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“DevOps&SRE Library” (@devopslibrary), 19,856 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/devopslibrary.
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.