与「kubernetes」相关的搜索结果

‼️ 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、硅谷、科技股、纳斯达克、英伟达市值、马斯克的相关内容了。 请把我带回到史前时代，谢谢🙏

Go 写的 Kubernetes 终端工具，灵感来自 k9s、Lens 和 lazygit。启动默认只读，避免手误搞坏集群，按 Shift+E 切到编辑模式。 功能挺全：集群概览、按资源类型浏览（支持 CRD）、编辑 YAML、看日志、进 Pod/Node Shell、删/扩/重启，还能显示对应的 kubectl 命令。

🚨 SlowMist TI Alert 🚨 MistEye has detected an active npm supply-chain attack compromising @redhat-cloud-services packages. Reported impact includes 31+ affected packages, about 116,282 weekly downloads, and 300+ GitHub repositories containing stolen credentials. The attack techniques show strong similarities to the previous Shai-Hulud npm campaign, including credential harvesting, malicious repository creation, and automated secret exfiltration. Public GitHub searches for the “Miasma: The Spreading Blight” marker, sorted by recent updates, still show newly appearing suspicious repositories, indicating that users are still being compromised. Potential attacker actions include GitHub/npm token theft, AWS/GCP/Azure credential theft, SSH key and Kubernetes secret collection, local environment and wallet data exfiltration, malicious GitHub repository creation, persistence, and destructive behavior if stolen tokens are revoked. Immediately remove or downgrade affected @redhat-cloud-services package versions, audit CI/CD workflows and dependency installs, rotate GitHub, npm, cloud, SSH, and wallet-related secrets, preserve logs, and rebuild exposed developer machines or runners from clean images. As always, stay vigilant! Live hunt: