Telegram RegisterThe public register of Telegram

Channel

Кубернетичек

@k8sjust

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,082subscribers

-1 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002089854870
TypeChannel
Username@k8sjust
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 August 2026
Measurements held2
Confirmed unchanged2 times, most recently 11 August 2026
On Telegramt.me/k8sjust

Growth

1,0821,0831,082.58 Aug 2026, 02:16 — 1,083 subscribers9 Aug 2026, 01:31 — 1,082 subscribers8 Aug 2026, 02:169 Aug 2026, 01:31
2 measurements taken within a single day, net -1. 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 1,082–1,083 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 01:311,082-1
8 Aug 2026, 02:161,083first reading

Engagement

20 posts held, back to 6 September 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.

ERR · 30 days
67.3%
avg views ÷ 1,082 subscribers
Avg views / post
728
1 post measured
Reaction rate
9.07%
reactions ÷ views · ER floor
Posts in window
1
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 July 2026
Posts held20 (6 September 202528 July 2026)
Views total728
Reactions total66
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:16 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.

Reaction mix

260 reactions across 19 posts, in 13 distinct kinds. The most used accounts for 31.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍8231.5%
3714.2%
🔥3312.7%
😢3011.5%
😁2710.4%
🫡2710.4%
🤯72.69%
🤔62.31%
🎉41.54%
🥴31.15%
👎20.769%
❤‍🔥10.385%
🤣10.385%

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 20 of the 20 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 260reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 September 2025 to 28 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.

Recent posts

28 Jul 2026, 13:35 UTC728 views66 reactionsread 8 August 2026

Перестал писать в этот канал, потому что писать стало нечего :) Канал, который был создан шутки ради для своих в одном душевном чатике, немного расширился на большую аудиторию. В канале писались вещи, которые автор узнавал в ходе работы или любопытства. Своими руками и временем. Но, в последнее время, мои знания проигрывают умению находить информацию у LLM. Последним гвоздем в гроб была информация, что SyncPeriod н

😢30🫡277👍2

7 May 2026, 10:16 UTC≈1,470 views14 reactionsread 8 August 2026

https://kubernetes.io/docs/reference/instrumentation/understand-psi-metrics/ Тем временем, psi метрики перешли в ga в версии 1.36 (в бете с версии 1.34). Да еще и сделали их неотключаемыми. Если кто не знает что это и зачем, можно почитать тут https://t.me/troubleperf/73

👍14

15 Apr 2026, 19:54 UTC≈1,810 views11 reactionsread 8 August 2026

https://t.me/ittales/699 Автор этой базы разработчик k0smotron. А вообще, еще было решение когда взяли архитектуру loki/mimir/thanos и других греческих богов и решили сделать на этом etcd-compatible решение с храненим в s3 - https://github.com/nadrama-com/netsy. Но T4 без gossip протоколов и сложной архитектуры, и с jensen тестами, branching лизами и тп. Моё почтение Алексею.

8🤔2👍1

31 Mar 2026, 11:39 UTC≈1,790 views5 reactionsread 8 August 2026

Тут вышла статья https://itnext.io/the-challenge-of-configmap-rollouts-in-kubernetes-1431398c0866 от Brian Grant (одного из оригинальных архитекторов Kubernetes). Статья как статья - ничего особенного, казалось бы, кроме ишью https://github.com/kubernetes/kubernetes/issues/22368. Даже представить не мог, что это может болеть у кого-то ещё в мире, где помимо решений из статьи есть kind: PodTemplate, который можно испо

👍3🔥2

9 Mar 2026, 07:01 UTC≈1,540 views7 reactionsread 8 August 2026

Так как автор блога начинал свою карьеру грузчиком мороженного в телекоме, то левым глазом он посматривает, что там в этом телекоме происходит интересного. Про SRv6 меня тема не сильно интересует: драфтов много, решения разных вендоров не совместимы (или не совсем совместимы), и скорее всего решение от Cisco победит, как всегда. В конечном счёте мне кажется, что SRv6 займёт нишевую позицию - вроде как хайп был, а мей

🔥42❤‍🔥1

28 Feb 2026, 10:55 UTC≈1,440 views15 reactionsread 8 August 2026

Меня в таких историях https://blog.zwindler.fr/en/2026/02/26/kyverno-killed-my-api-server.-again./ интересует вот что: многие компании разделяют администрирование кластеров Kubernetes по компонентам - условно, Kyverno и Cilium NetworkPolicy за ИБ-командой, control plane и CNI за кубовыми админами, CSI за командой хранилищ. Как они траблшутят в момент обновления кластера, когда что-то идёт не так? Насколько дольше ра

👍11🤔4

4 Feb 2026, 13:22 UTC≈1,810 views3 reactionsread 8 August 2026

https://github.com/kubernetes-sigs/multicluster-runtime Клевый проект. Я немного его тестирую. Пока не принято решение, что лучше для нашего проекта: один контроллер пер кластер, и один большой оркестратор на все. Или волбще - гибрид. Проект уже довольно в рабочем состоянии. Но, если брать его сейчас, то нужно быть готовым в след релизе что-то переписывать :) У openkruise было похожее решение, но в него перестали ко

👍3

27 Jan 2026, 15:48 UTC≈1,890 views14 reactionsread 8 August 2026

Люблю openkruise. Он меня уже столько раз выручал. Вот и сейчас, есть задача, чтобы не менялась топология у подов без надобности, нужно чтобы они шедулились на туже ноду, где были (по возможности). И пока я думал, делать это через mutation webhook или писать свой шедуллер, решил глянуть, а не реализрвали ли это уже разработчики алибаба клауд (да, я ленивый человек, если можно не просить ллм писать самому, то этого

🔥131

27 Dec 2025, 20:52 UTC≈3,880 views13 reactionsread 8 August 2026
Photo

Я прикалывался над этим проектом. Не думал, что там может быть что-то серьезное с таким замахом. Оказалось, этот проект идет под крылом китайского аналога Google Summer of Code, только называется он - RISC-V Rust for Cloud Native. Под этим же крылом выпустили https://github.com/rustfs/rustfs, например. Можно было бы подумать, что они это делают, потому что официально разработчики куба не поддерживают RISC-V архитекту

🔥8😁31👍1

23 Dec 2025, 19:32 UTC≈1,670 views3 reactionsread 8 August 2026

https://github.com/etcd-io/etcd-operator https://github.com/aenix-io/etcd-operator Вот уже больше года прошло с той, на мой вкус, некрасивой ситуации. Можно сравнить, что получилось. У одного продукта, контрибьютит один человек и минорно. У второго, по-сути двое и то же минорно. Да и в целом развивается ни шатко ни валко. После стартового запала, люди ожидаемо поотпадали и у официального варианта. Может я проспустил

👍3

2 Dec 2025, 22:44 UTC≈3,090 views16 reactionsread 8 August 2026

https://victoriametrics.com/blog/kubernetes-cpu-go-gomaxprocs/ Попалась замечательная статья. Много по полочкам разложено. Особенно упомянули формулу расчёта cpu weight для cgroupv2, которую хотят дополнительно разжевать https://github.com/kubernetes/website/pull/52793/files. Но есть нюанс (не в претензию к статье, она отличная) What's this static policy about? With static, Kubernetes can give certain containers ex

👍16

28 Nov 2025, 09:26 UTC≈1,360 views1 reactionsread 8 August 2026

https://github.com/fluxcd/helm-controller/pull/1365 Продолжение истории) Пызы: Стефан, похоже одобряет

🔥1

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

Citation-graph rank

Citation-graph rank — 985,239 of 1,183,361entries 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.

Mentions

Named by 1 registered channel — 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.

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

“Кубернетичек” (@k8sjust), 1,082 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/k8sjust.

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.