volcano
k8s-scheduler-extender-example
Our great sponsors
| volcano | k8s-scheduler-extender-example | |
|---|---|---|
| 2 | 1 | |
| 3,744 | 174 | |
| 3.3% | - | |
| 9.1 | 0.0 | |
| 1 day ago | 7 months ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
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.
volcano
-
Can we specify nodeSelector inline for a kubectl command
Also, if you are creating bare pods, this sounds like batch scheduling and you should consider using Jobs instead, to have a pod controller. And then you could also consider the https://volcano.sh/ scheduler if it has a fitting scheduling plugin for your use case.
-
My Journey With Spark On Kubernetes... In Python (1/3)
For our experiments, we will use Volcano which is a batch scheduler for Kubernetes, well-suited for scheduling Spark applications pods with a better efficiency than the default kube-scheduler. The main reason is that Volcano allows "group scheduling" or "gang scheduling": while the default scheduler of Kubernetes schedules containers one by one, Volcano ensures that a gang of related containers (here, the Spark driver and its executors) can be scheduled at the same time. If for any reason it is not possible to deploy all the containers in a gang, Volcano will not schedule that gang. This article explains in more detail the reasons for using Volcano.
k8s-scheduler-extender-example
-
Can we specify nodeSelector inline for a kubectl command
Thank you for the response r/EmiiKhaos, I have initially started with the custom scheduler that you have mentioned, but i couldn't be successful, the pod is not getting scheduled, I have followed this github repo https://github.com/everpeace/k8s-scheduler-extender-example, all the steps, but pod goes into pending state.
What are some alternatives?
kube-batch - A batch scheduler of kubernetes for high performance workload, e.g. AI/ML, BigData, HPC
spark-operator - Kubernetes operator for managing the lifecycle of Apache Spark applications on Kubernetes.
argo - Workflow Engine for Kubernetes
singularity-cri - The Singularity implementation of the Kubernetes Container Runtime Interface
warewulf - Warewulf is a stateless and diskless container operating system provisioning system for large clusters of bare metal and/or virtual systems.
charts - ⚠️(OBSOLETE) Curated applications for Kubernetes
kubernetes-operator-roiergasias - 'Roiergasias' kubernetes operator is meant to address a fundamental requirement of any data science / machine learning project running their pipelines on Kubernetes - which is to quickly provision a declarative data pipeline (on demand) for their various project needs using simple kubectl commands. Basically, implementing the concept of No Ops. The fundamental principle is to utilise best of docker, kubernetes and programming language features to run a workflow with minimal workflow definition syntax. It is a Go based workflow running on command line or Kubernetes with the help of a custom operator for a quick and automated data pipeline for your machine learning projects (a flavor of MLOps).
helm - The Kubernetes Package Manager [Moved to: https://github.com/helm/helm]