@OnlyXuanwo: Kubernetes developers simply don't understand how to deploy services. This kind of thing — separate process and configuration management — services should never run in a Pod. Just start each service in its own tmux session. When a restart is needed, write a while true loop; if it crashes, it automatically restarts. Performance...

X AI KOLs Timeline News

Summary

A developer criticizes Kubernetes' deployment method as too complex, advocating for using tmux sessions and while true loops to simply manage service processes, believing this approach has sufficient performance and is easy to maintain.

Kubernetes developers simply don't understand how to deploy services. This kind of thing — separate process and configuration management — services should never run in a Pod. Just start each service in its own tmux session. When a restart is needed, write a while true loop; if it crashes, it automatically restarts. The performance fully meets requirements. How many services can a company have? Even if you launch ten new services a day, that's only 3650 processes in a year. Just run top and see which one crashed, that's it.
Original Article

Similar Articles

@xfgong: Despite the abundance of open-source Sandbox services, none fully meet my needs. The two core requirements are: 1. The rootfs should not require snapshots, which means it should be cloud storage like virtual machines rather than local disks. This mainly addresses availability un…

X AI KOLs Timeline

The author discusses the shortcomings of open-source Sandbox services and proposes two core requirements: rootfs should use cloud storage to improve availability during node failures and reduce pause latency, and the /workspace file interface should be usable even when the sandbox is not started. They also emphasize building on the Kubernetes ecosystem rather than maintaining a separate cluster.

@LuBtc888: Seriously, I barely touch tmux for multi-terminal management anymore. With http://herdr.dev and http://muxy.app, these two tools kick tmux's cumbersome configuration out of the game. No need to memorize complex shortcuts, no need to fiddle with config files—ready to use out of the box, a blessing for the lazy. Productivity tools...

X AI KOLs Timeline

Introduces two terminal multi-window management tools, Herdr and Muxy. Herdr is a Rust-based native terminal proxy runtime that supports persistence, mouse operations, and proxy state management, serving as a tmux alternative.

Show HN: K10s – A Clickable Kubernetes TUI (Go, Bubble Tea)

Hacker News Top

Show HN: k10s 是一个用 Go 和 Bubble Tea 构建的可点击 Kubernetes 终端 UI,作为 k9s 的现代化替代,提供鼠标操作、全局搜索、延迟 informer 以实现即时启动,并内置具备集群上下文感知能力的 AI 助手。

@GitHub_Daily: Use tmux to manage terminal sessions, opening multiple windows in the terminal that can keep running in the background even after closing. But now, with multiple Agents running at the same time, automating terminal tasks with tmux requires writing a bunch of scripts, which is cumbersome. So a developer built rmux from scratch in Rust, designed specifically for Ag…

X AI KOLs Timeline

Introducing rmux, a modern terminal multiplexer written in Rust, designed for AI Agent and automation scenarios. It coordinates multiple Agents running simultaneously, is compatible with over 90 tmux commands, and offers a Python SDK and browser-based session sharing.