Telegram RegisterThe public register of Telegram
Telegram profile photo for k8s (in)security

Channel

k8s (in)security

@k8security

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

13,332subscribers

+386 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-1001390522820
TypeChannel
Username@k8security
DescriptionКанал о (не)безопасности Kubernetes + микросервисных, контейнеризированных приложений. Ведет команда www.luntry.ru #ZST99 Вопросы, идеи, предложения => @Qu3b3c https://knd.gov.ru/license?id=673ddbc21039886b1d03b7ce&registryType=bloggersPermission
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/k8security

Topic

Hacking & security — 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 11 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 the other topics.

Growth

12,94613,33213,1396 August 202610 November 2026
63 measurements spanning 97 days, net +386. 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 12,888–13,390 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
10 Nov 2026, 23:5613,332+3
9 Nov 2026, 12:5513,329+12
8 Nov 2026, 03:5113,317+7
7 Nov 2026, 01:1713,310-1
6 Nov 2026, 04:0713,311-2
5 Nov 2026, 01:1913,313+1
4 Nov 2026, 01:5713,312+3
3 Nov 2026, 05:1713,309-5
31 Oct 2026, 23:3513,314-3
31 Oct 2026, 00:3613,317+10
30 Oct 2026, 03:3913,307+4
29 Oct 2026, 03:0813,303+7
28 Oct 2026, 01:3613,296+6
27 Oct 2026, 01:1813,290-4
26 Oct 2026, 01:5013,294-2
25 Oct 2026, 03:2913,296+2
24 Oct 2026, 05:5513,294+9
23 Oct 2026, 08:4913,285-1
22 Oct 2026, 10:1913,286+16
21 Oct 2026, 03:2813,270first reading

Engagement

72 posts held, back to 9 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 66 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
26.1%
avg views ÷ 13,332 subscribers
Avg views / post
3,480
23 posts measured
Reaction rate
0.516%
reactions ÷ views · ER floor
Posts in window
23
of 72 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 11 November 2026
Posts held72 (9 July 2026 – 11 November 2026)
Views total80,063
Reactions total413
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 08: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

Photos
≈1,200
Videos
≈2
Links
≈1,810

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 34s
Average length
1m 34s

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.

Reaction mix

1,290 reactions across 67 posts, in 21 distinct kinds. The most used accounts for 36.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥46536.0%
👍41732.3%
❤27421.2%
🙊211.63%
🤔181.40%
❤‍🔥151.16%
🥰120.93%
🌚110.853%
✍100.775%
💯90.698%
💩70.543%
🥱70.543%
😱50.388%
🤡50.388%
👎40.31%
⚡20.155%
👏20.155%
🙏20.155%
🤮20.155%
👀10.078%
1 further kind10.078%

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

Measured over the 72 most recent posts we hold, published 9 July 2026 to 11 November 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

Telegram’s own ‘edited’ marker: 1 of 23 posts held from the last 30 days (4.35%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 06:28 UTC833 views6 reactionsread 11 November 2026
Photo

Сейчас в северной Америке проходит KubeCon + CloudNativeCon 2026 и завтра будет последний день, но уже сейчас на сайте доступны слайды с ряда презентаций (видео обычно становится доступно в течении месяца). Нам, конечно, в первую очередь интересна категория докладов Security (но часто на эту тему попадают и в другие категории). И нельзя не отметить категорию AI Inference + Agentic.

👍3🔥2🥰1

Signed Дмитрий Евдокимов

10 Nov 2026, 11:43 UTC≈1,640 views24 reactionsread 11 November 2026
Photo

Всем, привет! 12 ноября мы с командой расскажем нашу историю получения сертификата ФСТЭК России на наше решение Luntry! В рамках вебинара мы расскажем: 1) Требования регулятора в области защиты контейнерных систем 2) Детали сертификации Luntry 3) Создание защищенной контейнерной системы вместе с Luntry Зарегистрироваться на вебинар можно тут.

🔥11👍6❤5🥰2

Signed Дмитрий Евдокимов

10 Nov 2026, 05:01 UTC≈1,970 views16 reactionsread 11 November 2026
Photo

Portainer представила третью версию платформы, в которой Kubernetes становится основным направлением развития. Docker Standalone, Swarm и Podman продолжат получать обновления безопасности, но новые функции будут разрабатываться преимущественно для Kubernetes. При этом существующие Docker-сценарии можно будет сохранить с помощью Portainer-D2K. Интереснее всего обоснование этого решения — опубликованная вместе со стат…

👍7❤5🔥4

Signed r0binak

9 Nov 2026, 05:00 UTC≈2,140 views12 reactionsread 11 November 2026

Уже 23 ноября в Москве состоится второй Kuber Conf от АОТ! Возможно вы пропустили, но создатели данного канала (в лице Дмитрия Евдокимова (Luntry)) входят в экспертный совет АОТ и активно участвуют в подготовке конференции. Но речь сегодня не об этом. Мы будем проводить на наш взгляд очень интересный круглый стол: «Kubernetes победил, и это проблема?». Король оркестраторов выбран единогласно — Kubernetes. Насколько…

👍7🔥4❤1

Signed Дмитрий Евдокимов

6 Nov 2026, 05:00 UTC≈3,670 views24 reactionsread 11 November 2026
Photo

В Docker Desktop для Windows обнаружена критическая уязвимость CVE-2026-112917 с оценкой CVSS 4.0 – 9.2. Проблема затрагивает конфигурации с WSL2 и позволяет непривилегированному Linux контейнеру обойти ограничение seccomp для сокетов AF_VSOCK, используя 32-битный системный вызов socketcall. В результате контейнер может получить доступ к службам хостовой системы и файлам Windows, доступным текущему пользователю. По …

🔥14👍5❤4💩1

Signed r0binak

5 Nov 2026, 04:59 UTC≈3,670 views18 reactionsread 11 November 2026
Photo

На нашем сайте Luntry стали доступны слайды "Реагирование на инциденты в Kubernetes для SOC"! А на сайте SOC Forum 2026 в разделе "Онлайн-трансляция" в зале Физика можно найти запись выступления. Любая обратная связь и вопросы по данному исследованию приветствуется в комментариях к данному посту!

🔥10❤5👍3

Signed Дмитрий Евдокимов

3 Nov 2026, 05:00 UTC≈3,620 views18 reactionsread 11 November 2026
Photo

Можно ли просто навесить на контейнер жёсткий seccomp профиль и считать проблему изоляции решённой? Нет, и дело не только в ошибках конфигурации. Seccomp контролируется тем же ядром, которое должен ограничивать, поэтому при эксплуатации kernel LPE атакующий потенциально может отключить эти ограничения. Наглядная демонстрация – обход стандартного seccomp профиля container runtime через установку старшего бита в аргум…

✍7🔥5❤4👍2

Signed r0binak

2 Nov 2026, 07:16 UTC≈3,330 views14 reactionsread 11 November 2026
Photo

При защите контейнерных приложений в Kubernetes (да и не только) с его обилием механизмов безопасности, подходов и инструментов многие часто задаются вопросом: "А что делать в первую очередь?". Это очень не простой вопрос так как при ответе на него нужно учитывать и модель угроз, и модели нарушителей для того или иного кластера. Но с учетом быстро меняющей реалий, касаемых возможностей атакующего с обилием новых кр…

🔥14

Signed Дмитрий Евдокимов

30 Oct 2026, 05:03 UTC≈3,830 views18 reactionsread 11 November 2026
Photo

AI-агенты не просто генерируют текст – они исполняют код, работают с файловой системой и обращаются к сети. В Kubernetes это создаёт риски выхода из контейнера, кражи секретов и lateral movement, особенно если агент обрабатывает данные, содержащие prompt injection. В статье Untrusted Code, Trusted Cluster Scaling Secure AI Agent Workspaces with GKE Agent Sandbox разбирается GKE Agent Sandbox – решение Google для изо…

👍8❤7🔥2👏1

Signed r0binak

29 Oct 2026, 06:01 UTC≈3,730 views21 reactionsread 11 November 2026

Прошел SOC Forum 2026 и хочется поделиться кулуарными инсайдами после общения с коллегами, отвечающими за SOC, реагирование, форензику в различных компаниях (внутренние и внешние SOC). Основные 3 момента: 1) Инцидентов связанных с контейнерами и Kubernetes стало куда больше 2) Использование GTFOBins превалирует над использованием какого-то специального ВПО 3) Скорость атакующих растет Касательно последнего пункта хо…

💯8❤5👍5🔥2🤔1

Signed Дмитрий Евдокимов

28 Oct 2026, 05:00 UTC≈3,820 views24 reactionsread 11 November 2026
Photo

AI агенты в Kubernetes требуют не только изоляции, но и контроля над действиями. Обычный контейнер не гарантирует достаточной защиты. Агент может работать с секретами, обращаться к сети и выполнять недоверенный код. В статье Isolation. Security. Scale. разбирают связку kagent и Agent Substrate для безопасного запуска агентов. Изоляция строится на двух уровнях – gVisor перехватывает системные вызовы, а microVM обеспе…

👍12🔥7❤2🤔2👀1

Signed r0binak

27 Oct 2026, 05:50 UTC≈3,350 views12 reactionsread 11 November 2026

Бессомненно можно сказать, что появление и бум AI-агентов дал новое дыхание технологиям виртуализации с акцентом на microVM! Опять же Microsoft выпустила NVX: An Ultra-Light Micro-VM Sandbox с поддержкой Linux/KVM, Linux/MSHV, Windows/WHP. не путать с проектом Microsoft eXecution Container (MXC), о котором мы недавно писали. Это родственные инструменты для безопасной изоляции (песочниц) ненадежного кода, созданные …

👍4🔥4❤2🙏2

Signed Дмитрий Евдокимов

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

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.

Mentions

Named by 7 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.

Names

Channels on the register whose handles appear in this channel's posts.

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&SRE Library
@devopslibrary · 19,870
Telegram ranks this channel #3 of 94 here — alongside 93 others — read 30 September 2026
DevOps by REBRAIN
@rebrain_devops · 28,735
Telegram ranks this channel #6 of 94 here — alongside 93 others — read 9 September 2026
Yandex Cloud
@yandexcloudnews · 23,943
Telegram ranks this channel #8 of 97 here — alongside 96 others — read 22 September 2026
DevOps community for love
@devopsforlove · 44,606
Telegram ranks this channel #15 of 95 here — alongside 94 others — read 9 September 2026
Пост Лукацкого
@alukatsky · 38,465
Telegram ranks this channel #17 of 89 here — alongside 88 others — read 31 August 2026
Codeby
@codeby_sec · 37,083
Telegram ranks this channel #22 of 76 here — alongside 75 others — read 1 September 2026
Selectel
@Selectel · 62,423
Telegram ranks this channel #22 of 96 here — alongside 95 others — read 21 August 2026
S.E.Reborn
@S_E_Reborn · 22,459
Telegram ranks this channel #23 of 66 here — alongside 65 others — read 20 September 2026
ДЕВОПСИНА | DevOps | Linux
@devopsina · 23,569
Telegram ranks this channel #24 of 90 here — alongside 89 others — read 18 September 2026
DevOps
@DevOPSitsec · 23,892
Telegram ranks this channel #26 of 90 here — alongside 89 others — read 18 September 2026
Информация опасносте
@alexmakus · 18,748
Telegram ranks this channel #27 of 85 here — alongside 84 others — read 5 October 2026
Offensive Xwitter
@OffensiveTwitter · 21,323
Telegram ranks this channel #27 of 53 here — alongside 52 others — read 25 September 2026
S.E.Book
@S_E_Book · 23,090
Telegram ranks this channel #27 of 64 here — alongside 63 others — read 19 September 2026
infosec
@it_secur · 63,440
Telegram ranks this channel #29 of 81 here — alongside 80 others — read 22 August 2026
Life-Hack - Хакер
@haccking · 63,021
Telegram ranks this channel #31 of 85 here — alongside 84 others — read 21 August 2026
ServerAdmin.ru
@srv_admin · 32,701
Telegram ranks this channel #32 of 96 here — alongside 95 others — read 5 September 2026
Investigation & Forensic TOOLS
@forensictools · 22,610
Telegram ranks this channel #37 of 74 here — alongside 73 others — read 20 September 2026
infosecurity
@tg_infosec · 26,845
Telegram ranks this channel #37 of 74 here — alongside 73 others — read 11 September 2026
Утечки информации
@dataleak · 117,768
Telegram ranks this channel #39 of 83 here — alongside 82 others — read 14 August 2026
Positive Technologies
@Positive_Technologies · 29,449
Telegram ranks this channel #40 of 87 here — alongside 86 others — read 9 September 2026
IT STAND
@ITSTAND_ORG · 164,814
Telegram ranks this channel #44 of 98 here — alongside 97 others — read 9 September 2026
Bash Days | Linux | DevOps
@bashdays · 23,621
Telegram ranks this channel #47 of 94 here — alongside 93 others — read 18 September 2026
Хакер — Xakep.RU
@xakep_ru · 40,313
Telegram ranks this channel #50 of 83 here — alongside 82 others — read 30 August 2026
BZD • Книги для программистов
@bzd_channel · 36,213
Telegram ranks this channel #51 of 57 here — alongside 56 others — read 1 September 2026

This channel appears in 43 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“k8s (in)security” (@k8security), 13,332 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/k8security.

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.