知识卡片
服务更新覆盖多个租户部署
同一微服务的新版本需要更新所有相关共享和专用命名空间。版本化配置与协调器可把一次开发发布传播到多个目标,使开发者不用逐租户操作;仍需管理应用顺序、故障和回退,而不是假定仓库变化等于全体更新成功。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- EKS (Kubernetes) SaaS: Architecture Patterns and Strategies · 查看原书依据
to build it, test, and release it. However, something needs to deploy this updated service to each of the three namespaces on the right. This is where Flux can deal with 1-to-many mapping and address the rollout of the new version of the Order service.
参考来源
- 位置:《Building Multi-Tenant SaaS Architectures》第10章《EKS (Kubernetes) SaaS: Architecture Patterns and Strategies》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Multi-Tenant SaaS Architectures/_epub-src/OEBPS/ch10.html)
- 结论依据:原文具体说明同一微服务的新版本需要更新所有相关共享和专用命名空间;本卡据此归纳机制及适用边界。
- 原始内容:to build it, test, and release it. However, something needs to deploy this updated service to each of the three namespaces on the right. This is where Flux can deal with 1-to-many mapping and address the rollout of the new version of the Order service.