Channel
@technologynote
On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
615subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001153288739 |
|---|---|
| Type | Channel |
| Username | @technologynote |
| Created | Between 1 February 2019 and 30 September 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/technologynote |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 23:36 | 615 | -1 |
| 27 Aug 2026, 06:44 | 616 | -1 |
| 21 Aug 2026, 02:04 | 617 | +1 |
| 8 Aug 2026, 03:03 | 616 | no change |
| 7 Aug 2026, 23:49 | 616 | first reading |
20 posts held, back to 15 August 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 24 May 2025. An engagement rate over an empty window would be a number about nothing.
https://github.com/dotnet/runtime/pull/115762#discussion_r2098573409 非常有趣的一個案例，裡面可以看到 1. 修復問題不會全面修正，講一個修一個 2. 修復問題考量的實作也是比較單純，需要reviewer 提及所有概念才會去實作 3. 底下的留言普遍都是認為這些反覆對話所花費的時間已經幣比自己寫還更花時間了… 繼續看下去😹😹
https://www.uber.com/en-TW/blog/migrating-ubers-compute-platform-to-kubernetes-a-technical-journey/ > Operating large clusters on Kubernetes posed challenges with managing the API server load to prevent bottlenecks, ensuring that the scheduler can handle the scale even with high pod churn, and dealing with fragmentation issues that arise from running large clusters with varied workloads. Large cluster 都必須要處理的 sched…
https://grafana.com/blog/2025/04/27/grafana-security-update-no-customer-impact-from-github-workflow-vulnerability/ Grafana 最近遇到關於 GitHub Action 中有一些漏洞，導致有人可以獲得一些 secret，不過團隊透過 alert 馬上觀察到這個現象並且趕緊修復
https://kubernetes.io/blog/2025/04/07/introducing-kube-scheduler-simulator/ 如果有想要自行開發 Kubernetes Scheduler 的團隊可以參考看看這個逐漸成熟的工具，透過 KWOK(Kubernetes WithOut Kubelet) 的方式來搭建環境 要特別注意的是，這種模擬的工具終究不能模擬真正的大流量，主軸是 scheduler 的演算法，主要是用來確認 scheduling decision 的抉擇，如果演算法的內容牽扯到大量線上即時狀況的話，那此工具也還是可能沒辦法幫忙模擬。
今日最大的 K8s 消息大概就是 Nginx CVE https://www.wiz.io/blog/ingress-nginx-kubernetes-vulnerabilities 簡單來說，這是一個眾多 CVE 的組合 CVE-2025-1097 CVE-2025-1098 CVE-2025-24514 CVE-2025-1974 前述三者都是在鋪成這塊，包涵 CVE-2025-24514 -> nginx.ingress.kubernetes.io/auth-url: "http://example.com/#;\ninjection_point" (這種 annotation 就會被產生一些不合適的 nginx config) CVE-2025-1097 -> nginx.ingress.kubernetes.io/auth-tls-match-cn: xxxx (也是一樣會產生不合適的 nginx con…
https://dev.to/sklarsa/how-to-add-kubernetes-powered-leader-election-to-your-go-apps-57jh 這主題滿少見的，探討如何用 k8s 內建的 lease 物件來幫你的應用程式撰寫簡易的 election 機制。 如果你是用 kubeadm 安裝的環境且走 HA 架構，內建的 controller/scheduler 裡面其實也是靠這些來完成相關選舉的
https://blog.cloudflare.com/multi-path-tcp-revolutionizing-connectivity-one-path-at-a-time/ Cloudflare 官方部落格撰寫的 MPTCP (Multi Path TCP) 的教學，相較於傳統 TCP 來說, MPTCP 透過不同的路徑同時傳送 TCP 封包，可以提升整體的 throughput 以及更好的可靠性(假如系統上有多張網卡，則可以同時一起傳輸） 文章內有更多的介紹，這篇文章寫得很清楚，雖然目前大部分環境實務上用不到，不過還是可以當作科普的方式來學習一些網路概念
https://thenewstack.io/year-in-review-containers-get-smaller-faster-more-secure/ 本篇文章大抵上整理了這一年容器的發展，其中比較有趣的應該是 networking 的部分。 過往都是採用 veth 的方式來處理所有的 container networking，而 Linux kernel 6.7 後則是正式支援 Netkit 這個基於 eBPF 框架的網路處理方式， 根據文章中的描述，其傳輸效能比傳統 veth 好非常多，更貼近實體機器的效能。 至於 Continaer Image 的打包，文章內提到幾個關鍵字 1. Distroless 2. Chainguard/Google 3. Ko (針對 golang 的容器化工具） 4. Apko 5. BuildPacks, BuildKit and Dagger, and Nix.
Title: OpenAI 服務重大停機事件後檢討 Source: https://status.openai.com/incidents/ctrsv3lwd797 摘要: 2024/12/11 OpenAI 發生了重大問題，15:16~19:38(PST) 中間各種服務都出現使用異常，本篇文章是關於針對該事件進行事後調查與分析的技術文章 OpenAI 的服務都是部署到 Kubernetes 環境中，而這次事件的原因就是因為部署一個 Telemetry 的服務到叢集中，基本上部署一個服務應該是不會有太多的影響，不過官方提到這次的部署，導致的現象是每個節點上的 Telemetry Pod 都會往 API Server 進行大量的互動，所以對 API Server 來說就會收到跟節點數量成正比的大流量。 以過往 OpenAI 的相關文件，其最大的 Cluster 是上千台節點，以這種規模下，整個 API Server 以及背…
https://atbug.com/patent-troll-targets-k8s-dsdn/ 滿有趣的一篇文章，大抵上就是某公司申請了一個 SDN 的架構，其中的分散式架構與 K8s 的設計類似，所以關於 k8s 架構以及 CNI 生態系用法可能會有相關的所屬之爭 然後 CNCF 官方還有一篇徵求各位提供證據的文章 https://www.cncf.io/blog/2024/11/13/announcing-the-inaugural-contest-for-the-cloud-native-heroes-challenge/ If you are aware of any publicly available materials (other than materials already listed in the “known references” tab of the contest information p…
Title: Istio Ambient 正式版發佈 Source: https://www.cncf.io/blog/2024/11/07/fast-secure-and-simple-istios-ambient-mode-reaches-general-availability-in-v1-24/ 內容摘要 Istio 1.24 的 Ambient 模式在沒有 sidecar 的情況下實現了更高效率和以及架構簡化的流量控制，這對網格架構管理帶來重大改進。透過降低資源需求，Ambient 模式讓使用者能更靈活地部署並確保安全性和效能。 此模式的推出無疑提升了 Istio 在 Cloud Native 環境中的價值，是對雲端原生基礎設施的一次有力創新。
Title: Karpenter：改變我們 Kubernetes 的維運方式 Source: https://medium.com/adevinta-tech-blog/the-karpenter-effect-redefining-our-kubernetes-operations-80c7ba90a599 摘要: 這篇文章分享了 Adevinta 團隊在採用 AWS Karpenter 後，如何通過動態配置計算資源來改進 Kubernetes 的維運經驗。文章詳細探討了 Karpenter 如何通過自動調整資源分配，應對各種 Kubernetes 內的管理複雜度，同時提升系統靈活性和成本效益。 vinta 發現使用 Karpenter 後，資源配置時間減少了 75%，維運成本降低了 50%。 Karpenter 的動態資源調整功能，使得叢集在高峰期能夠靈活應對流量變化，平均提升了 30% 的資源利用率。文章還列舉了具體…
Showing the 12 most recent of 20 posts we hold for @technologynote. 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.
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 1 seed channel's Telegram-generated recommendation list 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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“矽谷牛的耕田筆記” (@technologynote), 615 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/technologynote.
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.