John Ternus is officially Apple CEO as of September 1st. Apple pushes back against OpenAI's attempts to delay its lawsuit against the AI company. What will Apple unveil at its upcoming September 'Surprise and Shine' event? And is Apple's immersive baseball event a hit?

• John Ternus is now the CEO of Apple.
• Tim Cook, the man who grew Apple by trillions of dollars.
• Apple's Ternus takes the reins as CEO, with AI as job No. 1.
• OpenAI's lawsuit delays cause more harm every day, says Apple.
• Potential Apple RAM supplier CXMT sues feds to take it off the supplier blacklist.
• China's CXMT makes breakthrough in advanced memory chips.
• Apple announces iPhone 18 Pro and foldable iPhone Ultra event: 'Surprise and shine'.
• What to expect from Apple's 'Surprise and shine' iPhone 18 Pro event on September 9.
• Leaker says iPhone Ultra will come in these colors, with one surprise.
• Apple takes first immersive baseball swings from the on-deck circle.

Picks of the Week

• Christina's Pick: GroxConnect/GroxStudio
• Andy's Pick: Lenovo ThinkVision M14
• Jason's Pick: Better Desktop by Knightscape in the Discord

Hosts: Leo Laporte, Andy Ihnatko, Jason Snell, and Christina Warren

Download or subscribe to MacBreak Weekly at https://twit.tv/shows/macbreak-weekly.

Join Club TWiT for Ad-Free Podcasts!
Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit

Sponsor:

• joindeleteme.com/twit-biz

How does AI change the intranet? Richard chats with Susan Hanley about her work helping organizations build great intranets and how tools like M365 Copilot are changing the intranet. Susan talks about the new reality of an intranet, where some users no longer go to the intranet directly but use an agent to retrieve the information they need. This impacts search statistics, but also means it's important to write pages that an agent can easily understand. The conversation also dives into the bane of all intranets - archiving data. LLMs can help with organizing data, but getting stale data out of view is essential. There are also retention policies and governance, and there's a role for these tools there too - the intranet is evolving!

Links

• SharePoint Skills

Recorded Aug 17, 2026

I am excited to announce that etcd RangeStream is graduating to beta in Kubernetes v1.37. Paired with etcd v3.7, it reduces the memory the API server and etcd need to read a large collection, and makes peak usage more predictable.

The cost of large reads

The API server serves most list and watch requests from its in-memory watch cache. Populating that cache requires reading a resource's full state from etcd, at startup and on every re-initialization. For a resource with many objects, or large ones, such as Pods, that read is expensive.

The API server already paginated these reads, asking etcd for a fixed number of keys at a time rather than the whole collection at once. But a page bounded by key count has no awareness of object size, so a page of large objects can still be very large. That makes memory usage hard to predict, and a bad combination of object size and concurrent reads can be enough to trigger an OOM. etcd's unary Range assembles each page in full before sending it, and the API server holds it while decoding, so the same payload sits in memory on both sides at once. Most of that cost lands on etcd, which is also where streaming helps most.

Streaming reads with RangeStream

etcd v3.7 adds a streaming version of that read, the RangeStream RPC. It takes the same RangeRequest as Range and returns the same result set, but instead of building the whole response up front, etcd splits it into chunks and streams them. Chunk size is tuned adaptively to the values being returned, so a collection of large objects is bounded by bytes rather than by a key count, and memory is freed as the stream progresses instead of being held until a whole page is assembled.

When the feature is enabled, the API server uses RangeStream wherever it reads a whole collection out of etcd. This includes watch cache initialization, and the fallback paths where a list request cannot be served from the cache and reads etcd directly. In either case the API server decodes each chunk as it arrives and releases it before pulling the next one, so neither side ever holds the whole collection.

Requirements

• Kubernetes v1.37 or later
• etcd v3.7 or later

RangeStream is used when the EtcdRangeStream feature gate is enabled on the kube-apiserver, which is beta and on by default in v1.37, and etcd is v3.7 or later. The API server resolves etcd's support at startup and also falls back at runtime if a call returns Unimplemented, so an API server paired with an older etcd keeps using the paginated Range path on its own. To turn it off, disable the gate:

--feature-gates=EtcdRangeStream=false

Confirming RangeStream is in use

The API server records streamed reads under their own operation label on its etcd metrics. A non-zero count here means RangeStream is in use:

etcd_request_duration_seconds_count{operation="listStream"}

If it stays at zero, the API server is still using the paginated Range path, most likely because etcd is older than v3.7.

Learn more

• KEP-5966: etcd RangeStream
• RangeStream in the etcd API guide
• Announcing etcd v3.7
• SIG etcd

If you have questions or feedback, join the #sig-etcd channel on Kubernetes Slack.