Channel
@kubernative
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,785subscribers
+57 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002046502224 |
|---|---|
| Type | Channel |
| Username | @kubernative |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/kubernative |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 20:11 | 1,785 | +6 |
| 6 Oct 2026, 02:55 | 1,779 | +3 |
| 29 Sept 2026, 07:38 | 1,776 | +11 |
| 19 Sept 2026, 11:16 | 1,765 | -3 |
| 15 Sept 2026, 04:40 | 1,768 | +4 |
| 11 Sept 2026, 14:38 | 1,764 | +5 |
| 7 Sept 2026, 08:37 | 1,759 | +3 |
| 2 Sept 2026, 06:21 | 1,756 | +1 |
| 30 Aug 2026, 03:18 | 1,755 | -3 |
| 27 Aug 2026, 09:56 | 1,758 | +4 |
| 24 Aug 2026, 00:46 | 1,754 | +2 |
| 20 Aug 2026, 10:55 | 1,752 | +4 |
| 17 Aug 2026, 13:43 | 1,748 | +4 |
| 14 Aug 2026, 13:27 | 1,744 | +10 |
| 10 Aug 2026, 19:37 | 1,734 | +5 |
| 7 Aug 2026, 09:51 | 1,729 | +1 |
| 6 Aug 2026, 22:00 | 1,728 | first reading |
20 posts held, back to 5 June 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 2 pages of 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
120 reactions across 20 posts, in 5 distinct kinds. The most used accounts for 41.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 50 | 41.7% | |
| 👍 | 36 | 30.0% | |
| 🔥 | 26 | 21.7% | |
| 🎉 | 7 | 5.83% | |
| 🤔 | 1 | 0.833% |
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 120 reactions 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 5 June 2026 to 6 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.
New free Kubernetes workshop Konrad Heimel announced the Kubernetes Practitioner Workshop, a GitHub repo that offers structured educational content for engineers looking to learn Kubernetes concepts and practice them. It comes with: - 28 topics (e.g., Containers, StatefulSet, The operator pattern, or Helm), each presented with 20-30 slides and accompanied with a practical lab requiring 15-30 minutes to complete; - …
👍5
What to expect in Kubernetes v1.37 The next Kubernetes release, v1.37, is scheduled later this month, on August 26th. It will come with several important deprecations (e.g., static Pods won't longer reference Secrets/ConfigMaps, the ipvs mode will be removed from kube-proxy) and over 20 new features, including Recreate update strategy for StatefulSets, volume health monitor, default Pod sysctls in Kubelet, Composite…
👍2❤1🔥1
Thought of running agents on Kubernetes more efficiently? Here’s a project from Google that you might find useful. Agent Substrate is an experimental system for running agents and similar workloads on Kubernetes at scale, providing specialised scheduling and controls to improve scalability and reduce latency. It relies on Kubernetes Pods and Pod autoscaling (but not K8s control plane) and manages the lifecycle of "a…
🔥2👍1
OpenTelemetry got a one-command Linux setup The OpenTelemetry Packaging SIG introduced a ready-to-use opentelemetry package for Linux distributions that installs the OpenTelemetry Injector together with the OpenTelemetry SDKs and auto-instrumentation packages for various programming languages (Java, .NET, Node.js, and Python). It is now available as an APT repository (for Debian, Ubuntu, and derivatives) and a YUM …
❤4
Kubeflow became a CNCF Graduated project The summer series of CNCF level-ups keeps going, and Kubeflow has just joined the list of the organisation’s most mature (i.e. Graduated) projects. The CNCF Technical Oversight Committee (TOC) voted for this graduation last Friday. Kubeflow is a machine learning toolkit for Kubernetes that serves as a foundation for K8s-based AI platforms. Its subprojects include Pipelines f…
❤7👍1
Confidential Containers became a CNCF Incubating project Another level up has just happened in the CNCF, with its TOC accepting moving Confidential Containers to the Incubating level. This project enables confidential computing by leveraging hardware-based TEEs (Trusted Execution Environments) to protect containers and data by encrypting data during computation. Confidential Containers started in 2021 by Red Hat, I…
👍2
Posted without readable text
👍5❤1
KubeSchool by Portainer As Neil Cresswell, CEO of Portainer, said on Reddit, one of his engineers recently asked him to help better understand Kubernetes architecture and components. Answering this request, he decided to go bigger and launched KubeSchool. It's an educational website featuring 15 chapters on Kubernetes basics for beginners. They cover the core ideas behind K8s, its main components, pluggable layers …
❤7
Buildpacks graduates, k8gb incubates Following the CNCF TOC votes that happened over the last weekend, two CNCF projects were promoted to the next level: 1. Buildpacks, a set of specifications and tooling that transform application source code into container images that can run on any cloud, became a Graduated project. It was started by Pivotal and Heroku in January 2018, joined the CNCF Sandbox in October 2018, an…
🎉6❤2🔥1
Posted without readable text
👍4
HAMi became a CNCF Incubating project HAMi was originally known as k8s-vGPU-scheduler and today stands for Heterogeneous AI computing virtualisation Middleware. It enables slicing a physical GPU into units by memory/core/device count, enforcing hard runtime isolation, and scheduling Pods using binpack, spread, and topology-aware policies. You can learn more about this project from this overview. HAMi joined the CNC…
🔥3🎉1👍1
William Rizzo, a CNCF Ambassador and Global Field CTO at Mirantis, announced his project, KubeSwift, which provides Kubernetes-native VM orchestration on Cloud Hypervisor. Here’s the idea behind KubeSwift: “KubeSwift runs virtual machines as Kubernetes workloads. You define a VM with a custom resource; controllers reconcile it into a Pod; inside that Pod, swiftletd launches a hypervisor.” (Cloud Hypervisor, on which…
👍5
Showing the 12 most recent of 20 posts we hold for @kubernative. 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.
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.
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.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Kubernative by Palark | Kubernetes news and goodies” (@kubernative), 1,785 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/kubernative.
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.