sidekick
High Performance HTTP Sidecar Load Balancer (by minio)
kube-batch
A batch scheduler of kubernetes for high performance workload, e.g. AI/ML, BigData, HPC (by kubernetes-retired)
| sidekick | kube-batch | |
|---|---|---|
| 1 | 3 | |
| 521 | 1,057 | |
| 2.5% | - | |
| 6.5 | 4.0 | |
| about 1 month ago | 11 months ago | |
| Go | Go | |
| GNU Affero General Public License v3.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sidekick
Posts with mentions or reviews of sidekick.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Node failure in a distributed minio cluster
Sidekick would be the recommended route (https://github.com/minio/sidekick). Other load balancers will work but can struggle with high I/O workloads and Sidekick is also incredibly simple to set up so that is a plus as well. Outside of some sort of load balancer, some people elect for RRDNS but that doesn't take nodes out of the available pool so isn't used as often.
kube-batch
Posts with mentions or reviews of kube-batch.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-03.
-
Volcano vs Yunikorn vs Knative
tldr; Knative Batch Job provider should support the respective coscheduling and kube-batch support. We had developed an in-house one for KubeFlow, from scratch. We had added Apache Arrow support into knative-serving with the respective CloudEvents interop layer, natively (i.e. secure shmem via IPC namespace, instead of message passing on the same host). We use it as a direct replacement for Apache Arrow Ballista, and had planned researching further DataFusion compat layer. Almost any modern ETL is pretty dubious without Apache Arrow.
-
Kubernetes Was Never Designed for Batch Jobs
Another aspect of batch jobs is that we’ll often want to run distributed computations where we split our data into chunks and run a function on each chunk. One popular option is to run Spark, which is built for exactly this use case, on top of Kubernetes. And there are other options for additional software to make running distributed computations on Kubernetes easier.
-
Scaling Kubernetes to 7,500 Nodes
> That said, strain on the kube-scheduler is spiky. A new job may consist of many hundreds of pods all being created at once, then return to a relatively low rate of churn.
Last I checked, the default scheduler places Pods one at a time. It might be advantageous to use a gang/batch scheduler like kube-batch[0], Poseidon[1] or DCM[2].
[0] https://github.com/kubernetes-sigs/kube-batch
[1] https://github.com/kubernetes-sigs/poseidon
[2] https://github.com/vmware/declarative-cluster-management
What are some alternatives?
When comparing sidekick and kube-batch you can also consider the following projects:
gobetween - :cloud: Modern & minimalistic load balancer for the Сloud era
volcano - A Cloud Native Batch System (Project under CNCF)