[{"data":1,"prerenderedAt":394},["ShallowReactive",2],{"tool-devtools-argo-cd":3,"footer-total":366,"related-devtools-argo-cd":367},{"id":4,"title":5,"author":6,"bestFor":7,"body":8,"category":324,"cons":325,"cover":331,"date":332,"description":333,"draft":334,"extension":335,"meta":336,"navigation":337,"notFor":338,"path":339,"pricing":340,"pros":343,"region":349,"score":350,"scoreBreakdown":351,"seo":356,"stem":357,"tags":358,"toolName":190,"updated":332,"url":363,"vendor":364,"__hash__":365},"tools\u002Ftools\u002Fdevtools\u002Fargo-cd.md","Argo CD 评测","元析评测","已经稳定运行 Kubernetes、想把线上变更收敛到 Git 仓库的 5 到 50 人平台团队",{"type":9,"value":10,"toc":296},"minimark",[11,15,23,26,29,45,48,52,55,59,62,66,69,73,76,79,83,86,90,93,97,100,104,107,111,114,117,173,176,179,253,259,263,267,270,274,277,281,284,287,290],[12,13,14],"h2",{"id":14},"结论先行",[16,17,18,22],"p",{},[19,20,21],"strong",{},"推荐,总分 8.6,开源版免费,自托管不收一分授权费。"," Argo CD 适合已经把 Kubernetes 跑在生产上、并且认定\"集群里的一切都该在 Git 里找得到出处\"的 5 到 50 人平台团队。装好控制器,给它一个仓库地址,它默认每 180 秒拉一次 Git,把里面的 Deployment、Service、ConfigMap 和集群实际状态逐字段比对;差异在界面上标出来,开了 selfHeal 之后,别人用 kubectl 手改的副本数会被改回去。",[16,24,25],{},"它不负责构建镜像,也不跑测试。CI 那段仍然交给 GitHub Actions、GitLab CI 或 Jenkins,Argo CD 只接管\"镜像已经推进仓库之后,怎么落到集群\"。如果你的资源清单里还有 RDS、DNS 记录、对象存储桶这类非 K8s 对象,那属于 Terraform 的地盘,它管不到。",[12,27,28],{"id":28},"这篇评测基于什么数据",[30,31,32,36,39,42],"ul",{},[33,34,35],"li",{},"官方文档:我们通读了 argo-cd.readthedocs.io 上 2.x 版本的 Application 规范、同步策略、Sync Waves 与 Hooks、ApplicationSet、RBAC 和 SSO 配置章节,文中的默认参数以文档为准。",[33,37,38],{},"项目治理:Argo CD 是 CNCF 毕业项目,代码仓库采用 Apache 2.0 许可,项目本身不卖订阅,官网也没有价目表。",[33,40,41],{},"版本变更记录:我们核对了 2.6 之后引入的多源 Application、ApplicationSet 的渐进式同步策略,以及 sync windows 的生效规则变化。",[33,43,44],{},"实测说明:我们没在 500 节点以上的集群做压测,文中关于 repo-server 内存占用与渲染耗时的描述来自官方运维文档和社区 issue,不是实测数字。",[12,46,47],{"id":47},"核心功能",[49,50,51],"h3",{"id":51},"声明式同步与差异可视化",[16,53,54],{},"一个 Application 绑定一个 Git 路径和一个目标集群的 namespace,Argo CD 把这个路径渲染出来的清单当作唯一真相。界面上每个资源有 Synced 和 OutOfSync 两种状态,点进去可以看到 live manifest 与 desired manifest 的逐行 diff,连某个 annotations 的拼写差异都能定位。Helm values、Kustomize overlay、纯 YAML 目录都能直接当源,渲染在服务端完成,CI 里不必先跑一遍 helm template。",[49,56,58],{"id":57},"applicationset一份模板铺开几十个集群","ApplicationSet:一份模板铺开几十个集群",[16,60,61],{},"集群从 3 个涨到 30 个时,逐个点鼠标建 Application 会让人崩溃。ApplicationSet 提供 list、cluster、git、matrix、pull request 几类生成器:cluster 生成器读的是 Argo CD 里注册的 cluster secret,新集群接进来就自动多出一整套应用;PR 生成器能给每个合并请求起一套临时环境,PR 关掉,资源跟着回收。模板里可以用 goTemplate 写条件分支,dev 和 prod 用不同副本数不必复制两份。",[49,63,65],{"id":64},"同步波次钩子与回滚","同步波次、钩子与回滚",[16,67,68],{},"默认情况下所有资源并发下发,谁先谁后不由你决定。Sync Waves 用注解 argocd.argoproj.io\u002Fsync-wave 排序,数字小的先执行,负数可以排到最前,常见做法是先建 namespace 和 CRD,再放业务负载。Hooks 分 PreSync、Sync、PostSync、SyncFail 四类,数据库迁移这类只跑一次的 Job 挂 PreSync 最稳。每次同步都留一条 revision 记录,出事在 History 里点回滚,或者用 argocd app rollback 指定版本号。",[49,70,72],{"id":71},"权限单点登录与通知","权限、单点登录与通知",[16,74,75],{},"RBAC 写在 policy.csv 里,细到\"某个 Google 组的成员只能对 prod 项目的应用执行 sync,不能 delete\"。SSO 走 Dex 或直接对接 OIDC,Keycloak、Okta、企业微信的 OIDC 都能接。通知由 argocd-notifications 控制器负责,同步失败、健康状态转 Degraded 时推送到 Slack、飞书或邮件,触发条件和模板可以按应用分别写。",[12,77,78],{"id":78},"评分明细",[49,80,82],{"id":81},"功能完整度9010","功能完整度:9.0\u002F10",[16,84,85],{},"K8s 声明式交付的主流程基本没有缺口:应用定义、多集群、模板化、排序、回滚、权限、通知全在。扣分点在于它不做渐进式发布,金丝雀和蓝绿要另装 Argo Rollouts;Secret 加密不在项目范围内;非 K8s 资源无从下手。",[49,87,89],{"id":88},"易用性7410","易用性:7.4\u002F10",[16,91,92],{},"Web 界面清爽,差异对比做得比多数同类工具好。但概念门槛摆在那里:Application、AppProject、ApplicationSet、Cluster Secret 得一个个弄明白,第一次搭高可用还要自己拼 Redis 和 HAProxy。repo-server 渲染慢的时候,报错信息往往只给一行,排查靠看 Pod 日志。",[49,94,96],{"id":95},"数据质量8610","数据质量:8.6\u002F10",[16,98,99],{},"同步状态是从集群 API 实时读的,不存在缓存骗人的情况,OutOfSync 就是真的不一致。短板在健康检查:内置脚本覆盖常见工作负载,自定义 CRD 不写 health check 就永远显示 Progressing,团队容易误判成部署没完成。",[49,101,103],{"id":102},"性价比9610","性价比:9.6\u002F10",[16,105,106],{},"授权费是零,集群数和用户数都不设限,这对预算紧的平台组几乎是白送。真正花钱的是控制面机器:3 个 controller 加 Redis,按云主机价格算每月几十美元,比任何商业 CD 平台的席位费都低。",[49,108,110],{"id":109},"客户支持8210","客户支持:8.2\u002F10",[16,112,113],{},"CNCF 项目的社区响应速度不错,Slack 频道和 GitHub Discussions 上常见问题当天有人回,官方文档在同类项目里算写得清楚的。但如果要 SLA 和兜底,只能从 Akuity 或云厂商买商业支持,那部分价格得单独谈。",[12,115,116],{"id":116},"定价说明",[118,119,120,136],"table",{},[121,122,123],"thead",{},[124,125,126,130,133],"tr",{},[127,128,129],"th",{},"方案",[127,131,132],{},"价格",[127,134,135],{},"说明",[137,138,139,151,162],"tbody",{},[124,140,141,145,148],{},[142,143,144],"td",{},"自托管开源版",[142,146,147],{},"免费",[142,149,150],{},"Apache 2.0,自行部署 controller、repo-server、Redis,不限集群与用户",[124,152,153,156,159],{},[142,154,155],{},"高可用自建",[142,157,158],{},"免费(只付服务器钱)",[142,160,161],{},"3 副本 controller 加 Redis HA、HAProxy,按云主机账单结算",[124,163,164,167,170],{},[142,165,166],{},"第三方托管控制面",[142,168,169],{},"官网未公开报价,需联系销售",[142,171,172],{},"Akuity 或云厂商代管,2026-11 核对",[16,174,175],{},"自托管省钱,但隐性成本要算清楚:repo-server 渲染大量 Helm chart 时吃 CPU,建议单独给节点;审计日志和 SSO 都要自己配,出问题也没有人接工单。团队只有一两个人时,这部分时间成本往往超过买托管服务。",[12,177,178],{"id":178},"和竞品对比",[118,180,181,197],{},[121,182,183],{},[124,184,185,188,191,194],{},[127,186,187],{},"维度",[127,189,190],{},"Argo CD",[127,192,193],{},"Flux CD",[127,195,196],{},"Spinnaker",[137,198,199,213,225,239],{},[124,200,201,204,207,210],{},[142,202,203],{},"定位",[142,205,206],{},"带界面的 GitOps 持续部署",[142,208,209],{},"CLI 优先的 GitOps 控制器组",[142,211,212],{},"流水线为中心的多云交付平台",[124,214,215,218,221,223],{},[142,216,217],{},"起步价",[142,219,220],{},"免费(自托管)",[142,222,220],{},[142,224,220],{},[124,226,227,230,233,236],{},[142,228,229],{},"同步方式",[142,231,232],{},"控制面主动拉 Git,一个实例管多集群",[142,234,235],{},"每个集群内部署,控制器各自拉取",[142,237,238],{},"以 pipeline 编排为中心,组件众多",[124,240,241,244,247,250],{},[142,242,243],{},"主要短板",[142,245,246],{},"非 K8s 资源覆盖不到,概念偏多",[142,248,249],{},"缺集中式 Web 界面,排查靠 flux CLI",[142,251,252],{},"需要专职维护 Clouddriver、Orca 等组件",[16,254,255,258],{},[19,256,257],{},"怎么选",":需要给产品、测试一个能点开看差异的页面,选 Argo CD;平台组习惯命令行、已经用上 Helm Controller 和 Kustomize Controller,Flux 更轻;只有在需要复杂多阶段发布编排、且有人专职维护时,才考虑 Spinnaker。",[12,260,262],{"id":261},"faq","FAQ",[49,264,266],{"id":265},"q-我们-ci-已经在-github-actions-里构建镜像了还需要-argo-cd-吗","Q: 我们 CI 已经在 GitHub Actions 里构建镜像了,还需要 Argo CD 吗?",[16,268,269],{},"A: 两者管的是不同段。Actions 负责跑测试、构建镜像、推 registry,推完之后集群怎么更新它不管。用 kubectl set image 或 helm upgrade 也能更新,但没人记录\"现在线上是哪个 commit\",回滚靠翻聊天记录。Argo CD 补的就是这段:Git 里改 tag,它同步,历史版本留着。",[49,271,273],{"id":272},"q-开了-auto-sync-和-prune结果把别人手建的-namespace-删了怎么防","Q: 开了 auto-sync 和 prune,结果把别人手建的 namespace 删了,怎么防?",[16,275,276],{},"A: prune 只删\"曾经由这个 Application 管理、现在从 Git 里消失\"的资源,手建的资源本来不在管理范围内,一般不会被误删。真正的风险是有人把资源加进 Git 又被移除。生产项目建议先关 prune,用 sync windows 限制可同步时段,再给 AppProject 加集群级白名单,只允许往指定 namespace 写。",[49,278,280],{"id":279},"q-数据库迁移必须在应用启动前跑完argo-cd-能保证顺序吗","Q: 数据库迁移必须在应用启动前跑完,Argo CD 能保证顺序吗?",[16,282,283],{},"A: 能,但要写对。把迁移 Job 放到 sync-wave 为 -1 的目录里,Deployment 用 0,PostSync 留给冒烟测试。Job 要设 hook-delete-policy: BeforeHookCreation,否则第二次同步会因为同名 Job 已存在而失败。迁移本身仍需幂等,Argo CD 只保证顺序,不保证脚本能重复执行。",[12,285,286],{"id":286},"评测方法说明",[16,288,289],{},"元析评测围绕功能完整度、易用性、数据质量、性价比、客户支持五个核心维度打分,每项满分 10 分,加权折算最终总分。文中涉及的开源许可、默认同步间隔与功能边界均于 2026-11 对照 Argo CD 官方文档核实,托管服务的计费以厂商结算页为准。",[16,291,292,295],{},[19,293,294],{},"最后更新",":2026-11-16",{"title":297,"searchDepth":298,"depth":298,"links":299},"",2,[300,301,302,309,316,317,318,323],{"id":14,"depth":298,"text":14},{"id":28,"depth":298,"text":28},{"id":47,"depth":298,"text":47,"children":303},[304,306,307,308],{"id":51,"depth":305,"text":51},3,{"id":57,"depth":305,"text":58},{"id":64,"depth":305,"text":65},{"id":71,"depth":305,"text":72},{"id":78,"depth":298,"text":78,"children":310},[311,312,313,314,315],{"id":81,"depth":305,"text":82},{"id":88,"depth":305,"text":89},{"id":95,"depth":305,"text":96},{"id":102,"depth":305,"text":103},{"id":109,"depth":305,"text":110},{"id":116,"depth":298,"text":116},{"id":178,"depth":298,"text":178},{"id":261,"depth":298,"text":262,"children":319},[320,321,322],{"id":265,"depth":305,"text":266},{"id":272,"depth":305,"text":273},{"id":279,"depth":305,"text":280},{"id":286,"depth":298,"text":286},"devtools",[326,327,328,329,330],"只认 Kubernetes 对象,云上的 RDS、DNS 记录、CDN 配置要另用 Terraform 管","不做构建、不做测试,镜像 tag 之前的环节全部依赖外部 CI","没有内置 Secret 加密,Sealed Secrets 或 External Secrets 需要自己接入","自定义 CRD 的健康检查要手写 Lua 脚本,不写就一直卡在 Progressing","高可用要自己拼 3 个 controller、Redis HA 和 HAProxy,运维门槛不低",null,"2026-11-16","Argo CD 评测:Apache 2.0 开源、自托管零授权费,默认 180 秒比对一次 Git 与集群状态,漂移能自动纠回;它不做镜像构建,也管不了云上非 K8s 资源,Secret 加密得自己补方案。",false,"md",{},true,"还没上 K8s、或者主要管理云主机与数据库等非容器资源的小团队","\u002Ftools\u002Fdevtools\u002Fargo-cd",{"free":337,"startingPrice":297,"currency":147,"billingPeriod":341,"notes":342},"一次性","Argo CD 采用 Apache 2.0 许可证,自行部署无授权费、不限集群数与用户数,官网无价目表;托管控制面由第三方(如 Akuity、云厂商)提供,官网未公开报价,需联系销售,2026-11 核对。",[344,345,346,347,348],"Apache 2.0 开源,自托管不限集群数和用户数,授权成本为零","Web 界面能逐行对比 Git 声明与集群实际状态,手动改过的副本数一眼可见","ApplicationSet 用 list、cluster、git 三类生成器,几十个集群只维护一份模板","sync-wave 注解加 PreSync\u002FPostSync 钩子,能把 CRD、迁移 Job、主应用排出先后","每次同步留一个 revision,回滚到上一个 Git 提交在界面上两步完成","global",8.6,{"features":352,"ease":353,"data":350,"price":354,"support":355},9,7.4,9.6,8.2,{"title":5,"description":333},"tools\u002Fdevtools\u002Fargo-cd",[359,360,361,362,190],"开发与运维","GitOps","持续部署","Kubernetes","https:\u002F\u002Fargoproj.github.io\u002Fcd\u002F","Argo Project(CNCF)","gEdT2kYznoTdRsAs4Js1Ye9L7Nk8KaD7BA76nqwR5BU",1016,[368,378,386],{"path":369,"toolName":370,"description":371,"score":352,"pricing":372,"vendor":370,"date":377,"category":324},"\u002Ftools\u002Fdevtools\u002Fgithub","GitHub","GitHub 评测:代码托管与协作的事实标准,免费版给无限私有仓库和每月 2,000 分钟 Actions,Team 每人每月 4 美元,企业版 21 美元。代码审查、CI、依赖包共用一个账号,适合 3 人以上研发团队,单人开源项目用免费版就够。",{"free":337,"startingPrice":373,"currency":374,"billingPeriod":375,"notes":376},"4","USD","月","Free $0(无限私有仓库、2,000 分钟 Actions\u002F月);Team $4\u002F用户\u002F月(3,000 分钟、2 GB Packages);Enterprise $21\u002F用户\u002F月(50,000 分钟、SAML SSO、审计日志 API)。价格 2026-11 核对官网 pricing 页,月付与年付同价。","2026-10-20",{"path":379,"toolName":380,"description":381,"score":350,"pricing":382,"vendor":380,"date":385,"category":324},"\u002Ftools\u002Fdevtools\u002Fcloudflare","Cloudflare","Cloudflare 评测:免费版就能挡掉大部分攻击,Pro 年付折合每月 20 美元、月付 25 美元,商业版每月 200 美元起,含 WAF 自定义规则。出海独立站首选,国内访问延迟高,纯国内业务要另配境内加速。",{"free":337,"startingPrice":383,"currency":374,"billingPeriod":375,"notes":384},"20","Free $0;Pro 年付 $20\u002F月、月付 $25;Business 年付 $200\u002F月、月付 $250;Enterprise 定制报价。Workers 付费版 $5\u002F月起。2026-11 核对官网 plans 页。","2026-11-07",{"path":387,"toolName":388,"description":389,"score":350,"pricing":390,"vendor":393,"date":332,"category":324},"\u002Ftools\u002Fdevtools\u002Fsupabase","Supabase","Supabase 评测:总分 8.6,Free 版 $0,Pro $25\u002F月起,含 10 万月活与 8GB 磁盘。会用一点 SQL、想省掉鉴权和文件存储搭建的独立开发者与小团队适合它;免费项目一周不活跃会被暂停,国内直连偏慢。",{"free":337,"startingPrice":391,"currency":374,"billingPeriod":375,"notes":392},"25","Free $0(500MB 数据库、1GB 文件存储、5 万月活、最多 2 个活跃项目,闲置 1 周暂停);Pro $25\u002F月起(含首个项目,10 万月活、8GB 磁盘、250GB 流量,超出按量计费,含 10 美元算力额度);Team $599\u002F月起;Enterprise 需联系销售。按量项与算力规格官网列有明细,2026-11 核对,以结算页为准。","Supabase Inc.",1794788226811]