Telegram RegisterThe public register of Telegram
Telegram profile photo for Kubernetes и кот Лихачева

Channel

Kubernetes и кот Лихачева

@Kubernetes_Likhachev

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

4,808subscribers

-9 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001598504220
TypeChannel
Username@Kubernetes_Likhachev
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/Kubernetes_Likhachev

Growth

4,8084,8184,8136 August 2026 — 4,817 subscribers6 August 2026 — 4,817 subscribers9 August 2026 — 4,818 subscribers12 August 2026 — 4,809 subscribers15 August 2026 — 4,808 subscribers6 August 202615 August 2026
5 measurements spanning 9 days, net -9. 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 4,807–4,820 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 16:574,808-1
12 Aug 2026, 04:264,809-9
9 Aug 2026, 06:424,818+1
6 Aug 2026, 06:344,817no change
6 Aug 2026, 06:174,817first reading

Engagement

21 posts held, back to 14 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
29.0%
avg views ÷ 4,808 subscribers
Avg views / post
1,400
4 posts measured
Reaction rate
3.74%
reactions ÷ views · ER floor
Posts in window
4
of 21 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 8 August 2026
Posts held21 (14 May 20268 August 2026)
Views total5,585
Reactions total209
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 05:17 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

306 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 30.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥9330.4%
👍9029.4%
7123.2%
💯3611.8%
😁82.61%
👏72.29%
🌚10.327%

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

Measured over the 21 most recent posts we hold, published 14 May 2026 to 8 August 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

8 Aug 2026, 08:45 UTC665 views10 reactionsread 12 August 2026
Photo

🥳Усато-полосатые в канале присутствуют? Пока Маркус наслаждается приятной погодой в Амстердаме, мы готовим новые новые технические разборы Друзья, какие темы для вас были бы интересны? Разберем любую тему по запросу!

9👍1

4 Aug 2026, 08:21 UTC≈1,210 views77 reactionsread 12 August 2026

👊👊ingress-nginx лёг, а в логах - пусто Readiness-проба падает, контроллер не отвечает, и ни одной внятной ошибки. Разгадка нашлась только в journalctl — и она уходит корнями в самое ядро Рассмотрел этот кейс в новой статье: https://telegra.ph/Istorii-s-dvojnym-dnom-08-03-2

👍28💯2017🔥12

28 Jul 2026, 15:02 UTC≈1,680 views26 reactionsread 12 August 2026
Photo

⭕️Просто случайный канал в Амстердаме У меня накопилось много фотографий Амстердама, но всего понемногу Друзья, поделитесь вашими городскими находками в комментариях!

🔥166👍4

23 Jul 2026, 13:50 UTC≈2,030 views96 reactionsread 12 August 2026

Друзья, привет! 👋 Написал заметку о секретах приложения для cluster admin Читать здесь: https://telegra.ph/Pryachem-sekrety-ot-cluster-admin-07-22-2

🔥3423👍23💯16

19 Jun 2026, 15:10 UTC≈2,450 views3 reactionsread 12 August 2026

Всем привет!🐈 Мы подвели итоги гранта на курс Kubernetes: продвинутый уровень и спешим поделиться результатами. Это было непросто — мы с командой учитывали вашу мотивацию и точность ответов в техскрининге. Полностью бесплатно курс получает: ➡️@dev_ooops Скидка 50% ➡️@AndrewElvis ➡️@alexei_emelin Скидка 30% ➡️@Oleg_Belsky ➡️@traveleronmoto ➡️@lehuspohus Поздравляем победителей!🔥 В ближайшее время с вами свяжется

👍3

19 Jun 2026, 10:56 UTC≈1,570 views10 reactionsread 12 August 2026
Photo

Любите ли вы «Властелина колец» так, как его любят в Нидерландах?🔥 Боромир всё равно любит сильнее ➡️Пруфы, кстати, вот: https://maps.app.goo.gl/vsT342xTodAKnp5S8

👏64

17 Jun 2026, 15:47 UTC≈1,320 views4 reactionsread 12 August 2026
Photo

Когда открыл документацию Kubernetes впервые — знакомая картина? Глаза разбегаются, в голове каша из Pod'ов, Service'ов, Ingress'ов и сотен других терминов. Именно эта ошибка новичков — пытаться объять необъятное в первый же день — и убивает всё желание разбираться дальше. Интенсив по погружению в Kubernetes мы строим ровно наоборот. За 7 дней вы соберёте чёткую, стройную картину: 🟠как устроен кластер и зачем все

👍2😁2

15 Jun 2026, 09:33 UTC≈1,390 views15 reactionsread 12 August 2026

Все еще не переехали на gateway api? Тогда этот гайд для вас⬇️ Вы наверняка слышали про CNCF. Крошечный консорциум, в рамках которого развиваются, наверное, все популярные и не очень cloud native инструменты. Они выпустили пост о том, как натолкнулись на разные проблемы в процессе миграции на gateway api. Разбираем https://www.cncf.io/blog/2026/04/13/ingress-nginx-to-envoy-gateway-migration-on-cncf-internal-servic

🔥10👍5

11 Jun 2026, 09:31 UTC≈1,320 views6 reactionsread 12 August 2026
Photo

Всем привет! Открываем прием заявок на гранты для потока Kubernetes: продвинутый уровень. Делали такое для базового, но на продвинутом работа глубже. Учить поднимать контейнеры не будем. Идем глубоко под капот: KEDA, написание своих операторов, отказоустойчивость БД в кластере. 🔥 Разыгрываем шесть мест: Одно со скидкой 100% Два со скидкой 50% Три со скидкой 30% ⚡️ Как принять участие: 1. Технический тест. Во

5👍1

10 Jun 2026, 09:34 UTC≈1,140 views9 reactionsread 12 August 2026

Иллюзия надежности: когда много точек присутствия не означает независимость от сетевых проблем Статья на хабре https://habr.com/en/articles/1035620/ натолкнула на идею поста. Не столкнешься с такой проблемой, и даже не задумаешься о ее существовании, но благо есть добрые люди, на опыте которых можно учиться и стелить соломки в таких случаях. Когда ты проектируешь геораспределенную систему, кажется, что взял сервер

👍9

8 Jun 2026, 09:40 UTC≈1,140 views4 reactionsread 12 August 2026
Photo

Всем привет! И с началом новой недели! Рад сообщить, что в Слёрм появилась автоматическая проверка устранения инцидентов 🔥 Система засчитывает инцидент только, когда все тесты пройдены. Это прямо как при работе с реальными задачами. Важен результат — устранение проблемы. Эта механика уже внутри практикума «Безопасность в Kubernetes». Что будет на практикуме: 🔸 Разбираем настоящие инциденты: Tesla Mining, SAP Sec

👍4

5 Jun 2026, 08:12 UTC≈1,300 views4 reactionsread 12 August 2026
Photo

Интенсив по погружению в Kubernetes Слёрм запускает 7-дневный марафон «Kubernetes: Быстрый старт» На интенсиве вы: 🔺Разберетесь в ключевых концепциях Kubernetes 🔺Поймёте, как он работает в реальных проектах 🔺Выполните практические задания 🔺Получите понятную картину того, как развиваться дальше Короткий, но полезный формат: За 40-60 минут в день вы поймете как устроен Kubernetes, зачем он нужен современному инженер

2🔥2

Showing the 12 most recent of 21 posts we hold for @Kubernetes_Likhachev. 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 — 89,554 of 1,481,306entries 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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“Kubernetes и кот Лихачева” (@Kubernetes_Likhachev), 4,808 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/Kubernetes_Likhachev.

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.