Telegram RegisterThe public register of Telegram

Channel

Кубертатный период

@kubertat

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

491subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001615747153
TypeChannel
Username@kubertat
DescriptionDevOps Underdog
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/kubertat

Growth

4916 Aug 2026, 12:19 — 491 subscribers6 Aug 2026, 18:47 — 491 subscribers6 Aug 2026, 12:196 Aug 2026, 18:47
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 490–492 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 18:47491no change
6 Aug 2026, 12:19491first reading

Engagement

17 posts held, back to 19 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 17 posts for this entry, the most recent from 8 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
151
Videos
10
Links
327

Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

184 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 22.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54249724700231040894122.3%
👍3921.2%
🦄3519.0%
3217.4%
custom 5300815226172612285168.70%
custom 545850181941410368084.35%
custom 546292111742338447873.80%
custom 536426506579923949752.72%
👎10.543%

Custom emoji. 5 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 16 of the 17 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 184reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 19 December 2025 to 8 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
122
across the posts below
Posts paid on
15
of 17 we hold a reading for · 88%
Most on one post
29
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kubertat. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 17 most recent posts we hold for this entry, published 19 December 2025 to 8 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

8 Jul 2026, 08:25 UTC251 views9 reactions1 Starread 6 August 2026

Еще один пример XY Problem В аппку летит кривой реквест (не тот хост, заголовок или еще что-то — неважно). И вместо того чтобы задаться вопросом почему начинается а давайте перепишем код, чтобы он переписывал реквест на правильный И это барахло вроде даже работает. Но проблема никуда не делась. Потом это всплывёт в самом тупорылом месте: на втором домене, в другом окружении, за CDN, после смены балансира, при пер

3👍3custom 54629211174233844782custom 53008152261726122851

7 Jul 2026, 12:26 UTC269 views9 reactionsread 6 August 2026

🛰 STUNner: если вам нужен способ протащить WebRTC media в приватный Kubernetes... ...а у нод нет публичных IP, а приложению нужно принимать WebRTC media traffic по UDP/TCP. И с media traffic уже начинается боль: UDP, NAT traversal, TURN, ICE и прочие радости WebRTC 🫠 📡 STUNner как раз решает эту проблему: он работает как Kubernetes-native TURN Gateway и позволяет завести WebRTC media traffic в кластер, не открывая

👍4custom 530081522617261228531custom 54249724700231040891

7 Jul 2026, 07:28 UTC262 views8 reactions18 Starsread 6 August 2026
Photo

fix(controller): preserve HPA-managed deployment replicas небольшой PR в Apache Superset Kubernetes Operator: исправил (конечно же с помощью ИИ 🤖) reconcile при включенном автоскейлинге Суть простая: если включен HPA, то оператор не должен управлять Deployment.spec.replicas. этим должен заниматься HPA. Иначе случается карусель, HPA скейлит вверх, а spec.replicas сразу терминирует поды. Еще один шильдик на GitHub з

4👍2🦄2

6 Jul 2026, 10:02 UTC239 views13 reactions1 Starread 6 August 2026
Forwarded from @ittales

Зацените какую штуку тут товарищ написал: https://github.com/crust-gather/crust-gather Она сохраняет стейт Kubernetes кластера в OCI-имадж (со всеми CRD, статусами, ивентами, подами и их логами) Потом его можно запустить локально и в нем покопаться обычным kubectl. Можно клода натравить, можно k9s, и т.п. Идеально подходит чтобы интегрировать в свой пайплайн. Написано на rust'е. Завтра будет рассказывать о ней на

👍5custom 530081522617261228551🦄1custom 54585018194141036801

2 Jul 2026, 12:45 UTC289 views7 reactions1 Starread 6 August 2026

We’re excited to introduce opensource vmestimator, a new component in the VictoriaMetrics ecosystem. vmestimator measures metrics cardinality across arbitrary label dimensions and exposes the results as Prometheus-compatible metrics. It helps to understand where cardinality comes from, track how it evolves over time, and build early-warning alerts before cardinality becomes a problem. If you’re operating Prometheus

5👍1custom 53642650657992394971

26 Jun 2026, 11:57 UTC413 views7 reactions1 Starread 6 August 2026
Forwarded from @zvlbtech

Наткнулся на очередную статью: «Zero-Downtime Deployments with Docker Compose — No Kubernetes Required». Автор прямо пишет - в индустрии, мол, массовое заблуждение, что для серьёзного прода нужен k8s. Не нужен. Тысячи проверок в минуту, мульти-регион, деплой по нескольку раз в день - и всё на компоузе. И тут он прав. Для одного хоста и пары сервисов Kubernetes - это из пушки по воробьям. Бесшовно перекатить контейнер

custom 530081522617261228542custom 54249724700231040891

9 Jun 2026, 06:49 UTC487 views8 reactions1 Starread 6 August 2026
Photo

Кто-нибудь пользуется GnuCash? Мне как обычно было нехуй делать утром и я запилил дашборд. Вдохновлялся нейрослопом от вайбкодера в интернете — https://cashdera.com/ Тут все по-дефолту: вместо уже имеющихся инструментов, которые не смогли осилить, чел решил наваять что-то "свое" с ИИ. https://gist.github.com/pashtet04/ebd3d1a4e0f5253a835b622f7d8a9913

👍3custom 536426506579923949721🦄1custom 54249724700231040891

5 Jun 2026, 07:23 UTC594 views14 reactions1 Starread 6 August 2026
Photo

Зумеры — они такие

🦄10custom 54249724700231040892custom 53642650657992394971custom 54629211174233844781

30 May 2026, 05:38 UTC692 views12 reactions1 Starread 6 August 2026

Кстати пост написан с применением ЕИ

👍5🦄3custom 542497247002310408921custom 53642650657992394971

30 May 2026, 05:32 UTC669 views17 reactions24 Starsread 6 August 2026

полгода назад ко мне пришли с вопросом, мол, есть какой-то сервис что-то про «ембеддинги», я особо не разбирался: ну еще какой-то микросервис где-то, хотим масштабирование «scale to 0». вводная при этом звучала конкретно: скейлиться нужно на основе кастомной метрики очереди — в очереди есть сообщения, значит поднимаем сервис, нет сообщений — 0. ну и я в общем-то почти не думая сразу вкинул про Keda, обрисовал что так

custom 542497247002310408965🦄4👍2

18 May 2026, 12:55 UTC586 views11 reactions27 Starsread 6 August 2026

ставит приложение в кубер helm чартом, через аргосд, в котором плагины на баше, которые через kustomize создают секреты из репо поиском по *.yaml с приправами башей для волта в какой момент чатгпт должен был встать и огреть его по голове?

🦄7custom 53008152261726122852custom 54585018194141036802

Showing the 12 most recent of 17 posts we hold for @kubertat. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 797,332 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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 6 August 2026 — this entry's latest reading, not the date you are reading this.

“Кубертатный период” (@kubertat), 491 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/kubertat.

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.