与「kubernetes」相关的搜索结果

Google 开源了 "Agent 工作负载的 Kubernetes"「AX」 AX 是为 Agent 设计的声明式编排运行时，你用 YAML 声明一个 Agent 任务，AX 负责在集群中沙箱化、配置环境、管控网络并大规模运行它。 开源地址： 它解决什么问题 项目的立论很清晰：Agent 是一种既有的编排体系都不匹配的新型工作负载。 · 它不像微服务(无状态、常驻)，Agent 会持续积累状态(对话记忆、工作区文件、工具会话); · 它不像批处理作业(跑完即弃)，Agent 大部分时间在等待，等模型响应、等工具返回、等人类审批，期间沙箱空转烧钱; · 它运行的是不可信代码，需要严格隔离；它还调用外部模型 API 和 MCP 工具服务器，需要网络与凭据管控。 架构：四个二进制 + Redis 四个二进制分工：ax(开发者 CLI)、ax-server(无状态 gRPC API)、ax-controller(调和循环)、ax-task-runner(每个任务容器内的 PID 1)。 核心原语：Task / Workspace / Model (+ Gateway) Task 是最小执行单元：带 CPU/内存限制的隔离沙箱。AX 刻意把它做得细粒度、可自由组合：一个任务可以是全部工作,也可以是任务树的根节点。生命周期用 status.phase + Conditions 表达,支持挂起(检查点保存状态)与恢复。 Workspace 是最有产品想象力的一层。它把“环境准备”声明化:列出需要的 Git 仓库、MCP 服务器、技能包,runner 在命令启动前物化好。更激进的是 generative workspace:你可以只写一句自然语言目标("搭一个 Python 3 开发环境"),首次启动时 runner 会派一个引导 Agent(Antigravity,需 GEMINI_API_KEY,默认限时 10 分钟)去实际安装工具链并验证依赖。声明一次,任意任务复用。 Model 把“用哪个模型、什么参数、密钥在哪”抽成命名资源,密钥引用 K8s Secret。轮换密钥、锁版本、调温度只需一次 ax apply。 沙箱与运行时细节 每个任务容器以 ax-task-runner 为 PID 1：启动元数据服务(端口 80,HTTP/1.1+h2c,暴露 /healthz、/readyz 和任务/工作区自省端点——Agent 不需要 SDK 就能读到自己的配置)、按绑定顺序初始化工作区、然后 fork 出 spec.command 并持续监管。命令退出后 runner 仍驻留,所以 ax ssh 和元数据服务在命令结束后依然可用。停机采用 SIGTERM + 10 秒宽限 + 强杀的两级策略。 安全模型有几处值得注意的门控：guest 服务(任意进程执行与文件读写,ax ssh 的底层)默认关闭,只在 debug: true 时开启——ax ssh 连不上未开启的任务是刻意的安全设计,不是故障;Gateway 用显式 allowlist 管控出站流量,并可向入站请求注入凭据,避免把 API key 直接塞进 Agent 环境。 路线图透露的方向 五大方向：Actor 架构深化、空闲检测自动挂起、有状态任务 fork、任务级 SPIFFE 身份做零信任 mTLS、runner 层自动采集 OpenTelemetry 遥测与结构化 Agent 轨迹。

ClusterMAX 3.0 is here! ClusterMAX 3.0 debuts with a comprehensive review of the neocloud industry, covering 77 providers. We increase our market view to cover 323 providers, up from 209 in ClusterMAX 2.0, 169 in ClusterMAX 1.0, and 124 in the original AI Neocloud Playbook and Anatomy article. We have now interviewed well over 200 end users of neoclouds as part of this research. We update our itemized list of criteria across 10 categories, and update our direct descriptions of our expectations for Slurm, Kubernetes, Standalone Machines, Monitoring Dashboards, and Health Checks. All of this content is live on our website. We encourage providers to use these lists when developing their offerings. We still consider these lists as an amalgamation of our experience interviewing end users, making them representative of the features that end users expect from their cloud providers. Nebius joins CoreWeave in the Platinum tier. While CoreWeave still sets the technical bar for others to follow, Nebius is now established as a provider that consistently commands a premium pricing over others. Strong business decisions by Nebius have put them in a position to serve an entire class of neolabs at seller’s prices. Google Cloud joins Oracle in the Gold tier. Azure moves to Silver, Fluidstack moves to Unavailable, and Crusoe drops to Bronze. Lambda, Firmus and TensorWave remain in Silver, while GMI moves up to Silver from Bronze. Many companies drop from Silver (or Gold) to Bronze or lower. We raise the bar this round as only 19 neoclouds globally achieve a Medallion rating. We establish a tier between Bronze and Underperforming: the Participation Ribbon tier. 15 providers join this rating, which more accurately describes our opinion that they do the bare minimum to get by.

‼️ BREAKING: An active npm supply chain attack has compromised at least 868 packages carrying over 2 billion monthly installs with a credential-stealing worm. Shai-Hulud is back. It started with the compromise of the GitHub account of the maintainer behind keyv, a library with roughly 127 million weekly npm downloads. A preinstall hook fires on npm install and drops a stealer that sweeps npm, GitHub, AWS, Kubernetes and Vault secrets, and then spreads to more maintainers.

新公司要看开张了，牛人请里边看，base上海 技术负责人（CTO ） 职位名称：技术负责人（AI API 中转站 CTO） 工作性质：全职 预期薪资：35,000–55,000 元/月（税前） 职位职责 • 负责公司核心技术架构设计与落地（多模型路由、统一 API 网关、计费系统、Key 管理、负载均衡） • 制定技术选型和稳定性策略，确保 7×24 高可用和低延迟（国内直联 + 海外多上游） • 带领团队进行快速迭代，主导核心功能开发与重构 • 负责安全、风控（Key 防刷、限流、日志脱敏）和合规（发票/合同意识） • 参与上游渠道谈判与技术对接，优化成本与稳定性 • 技术团队管理与 Code Review，构建可扩展的架构体系 任职要求 • 5+ 年大型项目或中台经验，精通后端架构（微服务、分布式系统、数据库优化） • 熟悉 AI/LLM 相关技术栈（OpenAI、Anthropic、Gemini、DeepSeek 等标准化协议）或有过同类项目经验优先 • 懂计费系统、流量控制、故障演练、监控告警（Prometheus/Grafana） • 熟悉 Redis、Kafka、Kubernetes 或类似高并发基础设施 • 有创业背景或快速成长经历，愿意承担初期所有技术风险与挑战 • 英语阅读能力（海外厂商文档） 优势加分项：有中转站、API 网关、跨境支付或企业 SaaS 经验者优先。 可以发我私信或者邮箱tristania_11@hotmail.com

Stack Overflow 和 Stack Exchange 是流量巨大的程序员问答网站和开发者网络 自2010年10月以来，所有Stack Exchange网站都运行在纽约（确切地说是新泽西州）数据中心的物理硬件上 2025年7月2日关闭了服役了15年的数据中心，拆除了所有服务器，拔掉了所有线缆，让这些曾经强大的机器谢幕 2021 年至 2023 年间，团队也开始拥抱云计算 将 Stack Overflow for Teams 实例迁移到了 Azure 新的基础设施涵盖 Cloudflare、nginx、Kubernetes、SQL Server、Redis 和 Elastic 云基础架构 SQL Server VMs 被分组到多个可用性组中，并加入到同一个托管 AD 中 所有应用程序和数据都将迁移到 GCP

We are open-sourcing blcli: an Agentic Infra Stack, battle-tested at 30M+ user scale. It allows coding agents like Codex or Claude Code to help manage your whole cloud infrastructure through code, PRs, dry-runs, and deterministic apply workflows. A solid & serious infra that can support to millions of users. This is a collaboration across multiple teams, the same stack that powers @AlvaApp, @Galxe, @GravityChain, and @ReahPlatform. Check it out here: Docs: blcli: Production stack template: Personal account starter: A common take today is: AI agents are useful for toy apps and prototypes, but not for serious infrastructure. The conclusion is wrong, because the issue is not that agents cannot work on real systems. The issue is that real infrastructure requires a large amount of expert context to get it correct in the first place, and even more context to guide agents through the next 18 months of iteration. Production infrastructure is not just a few Terraform files or Kubernetes YAMLs. It includes: cloud projects IAM boundaries networking VPC / subnet / firewall design Terraform state and backend management Kubernetes clusters cluster add-ons secrets management Git-based deployment workflows observability and telemetry (logs, metrics, traces. All integrated together and ready for your Agents to debug live on your prod env) databases, often self-hosted for cost efficiency and control environment separation: stg / beta / prd operational runbooks rollback paths production failure patterns Most of this knowledge usually lives in senior engineers’ heads, internal docs, shell scripts, Slack threads, old runbooks, and lessons learned from real incidents. If an agent does not have that context, of course it will build toy infrastructure. So the real question is: How do we package production infrastructure expertise into a form that AI agents can read, reason about, modify, and operate safely? That is what blcli does. At its core, blcli is a CLI tool plus a whole package of best practices of Infrastructure as Code. The key design principle is simple: Agents are already very good at reading and modifying code. So we make infrastructure code-first. The generated repo is intentionally self-explanatory. An agent can open the repo and understand what happened, and what's next. Who blcli is for? We built blcli for two types of users. 1. Product teams that need to scale beyond prototypes The first group is teams building real products that need infrastructure capable of growing beyond the prototype stage. These teams want the speed of AI-assisted development, but they cannot afford toy infrastructure. 2. Frontier labs and agent teams building self-improving systems The second group is frontier labs, data companies, and agent teams that need infrastructure not just to run applications, but to train, evaluate, and improve agents. If you are building coding agents, infra agents, or long-horizon autonomous systems, blcli stack is a good agent harness/env. Authors: @SiriJhui @p0pUBhv35I8308 @alvinFu1 @ryan4yin @algoxstonk

本人不想再听到任何关于 美光、半导体、大语言模型、LLM、三星、海力士、ChatGPT、编程、Agent、Codex、Claude Code、CUDA、GPU、H100、B200、台积电、ASML、NVIDIA、黄仁勋、OpenAI、Anthropic、Gemini、Grok、DeepSeek、Qwen、、Transformer、Prompt、Token、Inference、API、Copilot、Cursor、Docker、Kubernetes、Linux、云计算、算力、A100、服务器、机房、晶圆、EUV、HBM、DDR5、量化、蒸馏、多模态、Scaling Law、AI融资、Benchmark、Stable Diffusion、Midjourney、AI视频生成、自动驾驶、机器人、SpaceX、硅谷、科技股、纳斯达克、英伟达市值、马斯克的相关内容了。

本人不想再听到任何关于 美光、半导体、大语言模型、LLM、三星、海力士、ChatGPT、编程、Agent、Codex、Claude Code、CUDA、GPU、H100、B200、台积电、ASML、NVIDIA、黄仁勋、OpenAI、Anthropic、Gemini、Grok、DeepSeek、Qwen、、Transformer、Prompt、Token、Inference、API、Copilot、Cursor、Docker、Kubernetes、Linux、云计算、算力、A100、服务器、机房、晶圆、EUV、HBM、DDR5、量化、蒸馏、多模态、Scaling Law、AI融资、Benchmark、Stable Diffusion、Midjourney、AI视频生成、自动驾驶、机器人、SpaceX、硅谷、科技股、纳斯达克、英伟达市值、马斯克的相关内容了。 请把我带回到史前时代，谢谢🙏