头盔和Kubernetes:工作是否有障碍? [英] Helm and Kubernetes: Is there a barrier equivalent for jobs?

问题描述

给定3个Helm图中的3个作业(A，B，C)，是否可以并行运行A和B作业，然后在两个作业都完成后立即启动C?考虑一下障碍，在前进之前，需要完成一堆东西.

Given 3 jobs (A,B,C) in 3 Helm charts, is it possible to run A and B jobs in parallel, then start job C as soon as both of them are finished? Think of a barrier, in which a bunch of stuff needs to be finished before moving on.

即使我将A和B图表作为C图表的子图表，所有这3个图表都是并行启动的.

Even if I put A and B charts as sub-charts for C chart, then all 3 are started in parallel.

我已经有了一个解决方法:为A和B作业完成添加外部检查，然后启动C.不过，如果存在基于Helm的解决方案，我还是更喜欢它.

I already have an workaround for this: add an external check for A and B job finishing, then start C. Still, I would prefer a Helm-based solution, if it exists.

推荐答案

Kubernetes不是批处理作业框架/计划程序，因此不符合您的高级批处理框架要求.

Kubernetes isn't a batch job framework/scheduler and does not fit your advanced batch framework requirements.

我的建议是使用真正的批处理框架，例如 Luigi ，该框架还支持在以下时间安排Luigi作业kubernetes. 请在此处中查看如何执行此操作的示例.

My recommendation would be to use a real batch framework like Luigi which also supports scheduling Luigi jobs on kubernetes. Look here for an example how to do this.

这篇关于头盔和Kubernetes:工作是否有障碍?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！