KAI Resource Management is an open source, Kubernetes-native resource management layer for KAI Scheduler. It is designed to add organizational and infrastructure abstractions such as projects, departments, node pools, queues, and workload placement.
The KAI Resource Management Helm chart source is available under
deployments/kai-resource-management-chart.
There is not yet a published release, so cluster administrators must currently
package the chart from source and supply compatible controller images.
KAI Resource Management is intended to provide:
- Project and department resource hierarchies.
- Node-pool management and scheduler partition configuration.
- Queue and workload-placement integration with KAI Scheduler.
- A Helm-based installation and upgrade experience for cluster administrators.
| Path | Purpose |
|---|---|
deployments/ |
Deployment assets, including the kai-resource-management-chart Helm chart. |
cmd/ |
Executable entry points, one subdirectory per binary. |
pkg/ |
Shared Go packages used by repository binaries and integrations. |
docs/ |
User, administrator, reference, and developer documentation. |
hack/ |
Development, generation, and repository-maintenance scripts. |
test/e2e/ |
End-to-end suites and the framework that runs them against a cluster. |
.agents/ |
Repository-owned agent skills and other shared agent assets. |
The repository intentionally uses one root go.mod and one root Makefile.
New to KAI Resource Management? Read the overview, then install it and run a workload through it with the quickstart.
| I want to | Read |
|---|---|
| Understand what this is | Overview |
| Install it and try it | Quickstart |
| Understand the objects I create | Concepts |
| Do one specific thing | How-to guides |
| Look up a field, label or condition | Reference |
| Configure the Helm chart | Chart documentation |
| Build and test the repository | Building from source |
The full documentation index lists everything, including maintainer material.
Examples and sample manifests belong alongside the documentation that explains
them. This repository does not use a separate top-level examples directory.
Contributions are welcome. Read CONTRIBUTING.md before opening a pull request. By participating, contributors agree to follow the Code of Conduct.
Security vulnerabilities must be reported privately as described in SECURITY.md.