Arbiter is an extendable scheduling and scaling tool built on Kubernetes. It’ll aggregate various types of data and take them into account when managing, scheduling or scaling the applications in the cluster. It can facilitate K8S users to understand and manage resources deployed in the cluster, and then use this tool to improve the resource utilization and runtime efficiency of the applications.
The input can be metrics from your monitoring system, logs from your logging system or traces from your tracing system. Then arbiter can abstract the data to a unified format，so it can be consumed by scheduler, autoscaler or other controllers. Arbiter can also add labels to your applications based on how the administrator defines the classification and the data it collects. User can understand the characteristics of each application and the overall placement across the cluster, and then tune the factors that can improve it.
-
Refer to Install and Run Arbiter for quick start.
-
Refer to helm installation
See our documentation on Arbiter Site for more details.
- Get the cluster metrics for resource usage, such as cluster capacity、system resource usage，reserved resource and actual resource usage
- Usage trend of various resources
- Grafana template to show cluster metrics
- Scheduling based on actual resource usage of node
- Classify the pod/deployment/statefulset/service based on the resource sensitivity and the baseline defined by the administrator
- Support grouping of nodes for resource isolation
- Oversold configuration of pod and node for temporary resource feed
If you want to contribute to Arbiter, refer to contribute guide.
You can get what we're doing and plan to do here.
- Define what's OBI(Observability Indicator) that can convert metrics/logging/tracing to an unified indicator, so we can use OBI for scheduler and scaler.
- Introduce a context to let user extend scheduler easily using Javascript, and let user write Javascript to implement schedule logic.
- Create a plugin framework that can integrate with different observability tools as input and generate OBI output, such as metric-server, prometheus etc...
- Create a command line tool called 'abctl' to get OBI for K8S resources
- Create sample use cases using current framework to show how it can work, including:
- Schedule Pod based on actual resource usage on nodes
- Schedule Pod based on node labels using different schedule policy
- Tag the pod/service for different resource sensitivity
- Schedule based on pod and node names/labels without define node affinity
- Reserve node resource in the scheduler extension
- Provide executor to demo how to use OBI to support various use cases.
- Use kube-scheduler-simulator to evaluate the effect of different schedule policy
- Support logging indicator in the observer plugins
- Enhance the executor framework, so the user can easily define actions based on the results of OBI.
- Allow to use Kubernetes scheduler policy dynamically in scheduler extension
- Add more samples to generate OBI to introduce popular indicators, so the user can use directly
- Support tracing indicator in the observer plugins
- Integrate with more monitoring/logging/tracing tools for more coverage
- Improve the timeliness of data for better scheduling or scaling
- Use time serial database to show the data trend for better visualization
- Integrate with existing Scheduler, HPA and VPA from open source community, so the user can use it out-of-the-box
- Add plugin management support to add/remove/update observer/executor/scheduler plugins.
If you need support, start with the troubleshooting guide, or create github issues