知识卡片
工作流与GitOps分工
书中示例由Argo Workflows编排集群外供应及租户配置生成,再把Helm发布配置提交仓库,由Flux协调实际集群状态。工作流负责步骤和依赖,GitOps负责期望状态落实;已提交配置不应直接当作资源已经就绪。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- EKS (Kubernetes) SaaS: Architecture Patterns and Strategies · 查看原书依据
At this point, we have a Helm chart that represents the configuration we want for our tenant, but it has not been applied to our EKS cluster. This is where Flux comes into the picture. Once our Helm chart is ready, we can commit to our repository (step 7). Flux will be listening to that repository to detect any updates.
参考来源
- 位置:《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)
- 结论依据:原文具体说明书中示例由Argo Workflows编排集群外供应及租户配置生成,再把Helm发布配置提交仓库,由Flux协调实际集群状态;本卡据此归纳机制及适用边界。
- 原始内容:At this point, we have a Helm chart that represents the configuration we want for our tenant, but it has not been applied to our EKS cluster. This is where Flux comes into the picture. Once our Helm chart is ready, we can commit to our repository (step 7). Flux will be listening to that repository to detect any updates.