知识卡片
节点与集群专用化更粗粒度
在命名空间之外将节点分配给租户,可减少底层计算共享;每租户独立集群则进一步分开运行环境,却增加成本、发布和管理规模。也可让一组租户共享一个集群。选择越粗不代表必然越好,仍要有对应的合规或负载理由。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- EKS (Kubernetes) SaaS: Architecture Patterns and Strategies · 查看原书依据
you’re anticipating supporting a large collection of tenants, this approach could also present scaling challenges. Again, it’s not invalid, it just feels a bit like overkill given the other options you may have. One variation of this approach would be to employ a pod-based deployment where you distribute groups of tenants across a collection of clusters (the term “pod” gets
参考来源
- 位置:《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)
- 结论依据:原文具体说明在命名空间之外将节点分配给租户,可减少底层计算共享;每租户独立集群则进一步分开运行环境,却增加成本、发布和管理规模;本卡据此归纳机制及适用边界。
- 原始内容:you’re anticipating supporting a large collection of tenants, this approach could also present scaling challenges. Again, it’s not invalid, it just feels a bit like overkill given the other options you may have. One variation of this approach would be to employ a pod-based deployment where you distribute groups of tenants across a collection of clusters (the term “pod” gets