#CNCF

Moving KubeRay under CNCF governance reduces the risk of vendor lock-in for teams running Ray on Kubernetes, since the operator now follows a neutral, community-driven process. Platform engineers and MLOps teams planning large-scale training or inference clusters should evaluate KubeRay as their default integration path, especially where managed Ray services from cloud providers already build on it. The PyTorch Foundation tie-in signals tighter alignment between the training framework and serving infrastructure ecosystems.

Official accountPyTorch@PyTorchSource

Agent permissions today accumulate invisibly across shell history, consoles and memory, so the real shift here is that sandboxing becomes a supply-chain artifact you can diff, sign and hand over instead of a snowflake setup. Developers building or deploying agents — especially anyone juggling MCP servers and tool tokens — can now lock a digest that covers both code and its permission envelope. Because the format is just OCI, it plugs into registries and CI pipelines ASEAN teams already run with Docker.

shao__meng@shao__mengSource

CNCF公开了招商银行用HAMi做AI调度的真实案例，金融场景落地参考价值很高。

量子位@量子位的朋友们Source